Golf event management system with scoring and location tracking

ABSTRACT

A score tracking system may include a tracking module, companion device, and location system. The tracking module may be configured to be carried by a player competing in a golf tournament. The companion device may be configured to receive an input corresponding to a stroke event and that includes a time stamp corresponding to an occurrence of the stoke event. The location system may collect or receive location data, which comprises or is used by the location system to generate a plurality of sets of location coordinates. Each set of location coordinates may correspond to a location of the tracking module at a specified time. The location system may pair the time stamp with a set of the location coordinates corresponding to the location of the tracking module at the occurrence of the stroke event.

CROSS-REFERENCES TO RELATED PATENT APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/986,703, filed Nov. 14, 2022, which is a continuation of U.S. patentapplication Ser. No. 17/841,660, filed Jun. 15, 2022, which issued asU.S. Pat. No. 11,607,601 on Mar. 21, 2023, the entirety of all of whichare incorporated herein by reference.

TECHNOLOGY

The present disclosure is related to management of golf events includingsystems and methods of score and location tracking broadly adaptable tomultiple network infrastructures.

BACKGROUND

Management of golf tournament play while also providing detailedlocation and score tracking for every shot requires a complexbehind-the-scenes dance that is made even more difficult due tovariability of course location and infrastructure. For example, prior toevery PGA TOUR event each golf course is mapped to create a digitalimage of each hole that is used as background information in order tocalculate exact locations and distances between any two coordinates,e.g., tee box and the player's first shot or the shot location and thelocation of the hole. Using the mapping data together with its ShotLinksystem, PGA TOUR collects location of every ball and scoring for everyshot for every round. In addition to pre-tournament mapping, theShotLink system also utilizes a complex and costly infrastructure thattakes days to set up and takedown and must be transported betweenevents. Successful operation of the ShotLink system is also dependent ona volunteer workforce of up to 350 volunteers per event. The tournamentdata provided by the ShotLink system has been proven to be invaluable tofans and players alike. However, the time, expense, and infrastructurerequired to operate the ShotLink system make it impractical for use atlower level tournaments.

What is needed are systems and methods for providing golf eventmanagement that provide accurate tracking operations in a portabledesign, requiring reduced setup time and personnel, and that are widelyadaptable to course conditions and infrastructures.

SUMMARY

In one aspect, a score tracking system may include a tracking module,companion device, and location system. The tracking module may beconfigured to be carried by a player competing in a golf tournament. Thecompanion device may be configured to receive an input corresponding toa stroke event and that includes a time stamp corresponding to anoccurrence of the stoke event. The location system may collect orreceive location data, which comprises or is used by the location systemto generate a plurality of sets of location coordinates. Each set oflocation coordinates may correspond to a location of the tracking moduleat a specified time. The location system may pair the time stamp with aset of the location coordinates corresponding to the location of thetracking module at the occurrence of the stroke event.

In one example, the stroke event includes ball hit, and the location ofthe tracking module at the occurrence of the stroke event is used as aproxy for location of a ball of the player carrying the tracking moduleresulting from a previous stroke.

In the above or another example, the tracking module operates as abeacon in a location network. The location network may utilizeultra-wide band positioning.

In any of the above or another example, the tracking module isconfigured to transmit the location data to the location system.

In any of the above or another example, the location system isconfigured to receive the location data from a location network, and thelocation network is configured to calculate the plurality of sets oflocation coordinates.

In any of the above or another example, the location data collected orreceived by the location system comprises locating data that thelocation system uses to calculate the location coordinates.

In any of the above or another example, the plurality of sets oflocation coordinates comprise sets of GPS coordinates.

In any of the above or another example, the plurality of sets oflocation coordinates comprise sets of ultra-wide band positioningcoordinates.

In any of the above or another example, the tracking module isconfigured to collect location data at predefined first intervals andtransmit the collected location data to the location system atpredefined second intervals, wherein the second intervals are greaterthan the first intervals.

In any of the above or another example, the location system isconfigured to segment holes of a golf course into zones, each zonecorresponding to a range of location coordinates. The location systemmay determine a current zone the tracking module is located from theplurality of sets of location coordinates.

In any of the above or another example, the companion device includes aninterface configured to receive the input corresponding to the strokeevent. The stroke event may comprise address and ball hit. The interfacemay include an indicator configured to the pressed to indicate that theplayer is addressing the ball and held until the player hits the ball toindicate that the ball has been hit.

In any of the above or another example, the companion device isconfigured to be carried by a scorer that accompanies a group of playersincluding the player. The companion device may be further configured toreceive inputs corresponding to stroke events for all players in thegroup.

In another aspect, a score tracking method includes receiving, from acompanion device, an input corresponding to a stroke event of a playercompeting in a golf tournament, wherein the input includes a time stampcorresponding to an occurrence of the stoke event; collecting orreceiving, by a location system, location data, wherein the locationdata corresponds to a location of a tracking module carried by theplayer, and wherein the location data comprises or is used to generate aplurality of sets of location coordinates, each set of locationcoordinates corresponding to a location of the tracking module at aspecified time; and pairing the time stamp with a set of the locationcoordinates corresponding to the location of the tracking module at theoccurrence of the stroke event.

In one example, the stroke event includes ball hit, and wherein thelocation of the tracking module at the occurrence of the stroke event isused as a proxy for location of a ball of the player carrying thetracking module resulting from a previous stroke.

In the above or another example, the tracking module operates as abeacon in a location network. In one configuration, the location networkutilizes ultra-wide band positioning.

In any of the above or another example, the tracking module isconfigured to transmit the location data to the location system.

In any of the above or another example, the location tracking system isconfigured to receive the location data from a location network, and thelocation network is configured to calculate the plurality of sets oflocation coordinates.

In any of the above or another example, the location data collected orreceived by the location system comprises locating data that thelocation system uses to calculate the location coordinates.

In any of the above or another example, the plurality of sets oflocation coordinates comprise sets of GPS coordinates.

In any of the above or another example, the plurality of sets oflocation coordinates comprise sets of ultra-wide band positioningcoordinates.

In any of the above or another example, the tracking module isconfigured to collect location data at predefined first intervals andtransmit the collected location data to the location system atpredefined second intervals. The second intervals may be greater thanthe first intervals.

In any of the above or another example, wherein the method furtherincludes segmenting holes of a golf course into zones, each zonecorresponding to a range of location coordinates, and determining acurrent zone the tracking module is located from the plurality of setsof location coordinates.

In any of the above or another example, the companion device may includean interface configured to receive the input corresponding to the strokeevent. The stroke event may include address and ball hit. The interfacemay include an indicator configured to the pressed to indicate that theplayer is addressing the ball and held until the player hits the ball toindicate that the ball has been hit.

In any of the above or another example, the companion device is carriedby a scorer that accompanies a group of players including the player,and the companion device receives inputs corresponding to stroke eventsfor all players in the group.

In any of the above or another example, the stroke event is input intothe companion device by a scorer viewing a live video of the golftournament.

In any of the above or another example, the stroke event is input intothe companion device by a scorer viewing a video replay of the golftournament.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the described embodiments are set forth withparticularity in the appended claims. The described embodiments,however, both as to organization and manner of operation, may be bestunderstood by reference to the following description, taken inconjunction with the accompanying drawings in which:

FIG. 1 schematically illustrates hardware and networking features of aSTTM system according to various embodiments described herein;

FIG. 2 schematically illustrates various elements and operatingenvironment components of a STTM system according to various embodimentsdescribed herein;

FIG. 3 illustrates zone features for location tracking according tovarious embodiments described herein;

FIGS. 4A & 4B illustrate various views of a tracking module according tovarious embodiments described herein, wherein FIG. 4A shows a face-onview and FIG. 4B shows a side view;

FIG. 4C illustrates a perspective view of a tracking module according tovarious embodiments described herein;

FIG. 4D illustrates various components of a tracking module according tovarious embodiments described herein;

FIG. 5A provides an overview listing of the tracking modules and theirassociated locations that are loaded into the device management systemaccording to various embodiments described herein;

FIG. 5B illustrates an example user interface generated by a devicemanagement system to provide tracking module management functionalitiesand present device management data for loaded tracking modules accordingto various embodiments described herein;

FIG. 5C illustrates a device assignment user interface that enables auser to perform device assignment operations according to variousembodiments described herein;

FIG. 6A illustrates a groupings engine user interface comprising agroupings management panel according to various embodiments describedherein;

FIG. 6B illustrates a groupings presentation by segment according tovarious embodiments described herein;

FIG. 6C illustrates a segment profile management interface that includesexample data elements of a segment profile along with definitions ofoptions to edit the data elements or create a new segment according tovarious embodiments described herein;

FIG. 6D illustrates an interface of a revision editor configured toadjust tee times using a “revise based on offset” methodology or a“revise using base time” methodology according to various embodimentsdescribed herein;

FIG. 6E illustrates a player status editor interface according tovarious embodiments described herein;

FIG. 6F illustrates a rounds engine interface comprising a roundsmanagement panel according to various embodiments described herein;

FIG. 6G illustrates a rounds engine interface for creating a playoffaccording to various embodiments described herein;

FIG. 7A illustrates a menu screen of the ST application according tovarious embodiments described herein;

FIG. 7B illustrates player descriptions election screen of the STapplication according to various embodiments described herein;

FIG. 7C illustrates a descriptive category selection screen of the STapplication according to various embodiments described herein;

FIG. 7D illustrates a descriptive characteristics selection screen for aselected descriptive category of the ST application according to variousembodiments described herein;

FIG. 7E illustrates a summary player details screen of the STapplication according to various embodiments described herein;

FIG. 7F illustrates a selection of the “select club” feature from thegroup screen of the ST application according to various embodimentsdescribed herein;

FIG. 7G illustrates selection of “iron” from the select club screen ofthe ST application according to various embodiments described herein;

FIG. 7H illustrates an interface for indicating “shot hit” using the STapplication according to various embodiments described herein;

FIG. 7I illustrates an “in the hole” prompt of the ST applicationaccording to various embodiments described herein;

FIG. 7J illustrates a group screen displaying a recorded stroke afterthe score has indicated “shot hit” using the ST application according tovarious embodiments described herein;

FIG. 7K illustrates a selection of the “from location” feature from thegroup screen of the ST application according to various embodimentsdescribed herein;

FIG. 7L illustrates a selection of available descriptive characteristicsfor selection in the “from location” screen of the ST applicationaccording to various embodiments described herein;

FIGS. 7M & 7N illustrate a group screen showing the transition of the“from location” from “fairway” back to “from location” after indicating“shot hit” using the ST application according to various embodimentsdescribed herein;

FIG. 7O illustrates a group page wherein the first two players havefinished the hole and the third player is on the green according tovarious embodiments described herein;

FIG. 7P illustrates recording a second shot off the tee recorded as aprovisional according to various embodiments described herein;

FIGS. 7Q-7S illustrate user interfaces of the ST application depictingthe work flow for recording a provisional shot that is ultimately used,resulting recordation of a penalty stroke according to variousembodiments described herein;

FIGS. 7T-7V illustrate user interfaces of the ST application depictingthe work flow for recording a penalty drop and indicating that thedropped ball is in play according to various embodiments describedherein;

FIG. 8A illustrates a presentation block user interface of a datamanagement tool of data management system including tool components inpresentation blocks according to various embodiments described herein;

FIG. 8B illustrates a group scorecard interface of the data managementtool according to various embodiments described herein;

FIG. 8C illustrates a team player stroke detail component of the datamanagement tool according to various embodiments described herein;

FIG. 8D illustrates a stroke event review viewer of the data managementtool according to various embodiments described herein;

FIG. 8E illustrates an all group presentation component of the datamanagement tool according to various embodiments described herein;

FIG. 8F illustrates an example interface of the data discrepancies panelcomponent of the data management tool according to various embodimentsdescribed herein;

FIG. 8G illustrates the presentation block user interface depictingconnections between presentation blocks of the tool components accordingto various embodiments described herein;

FIG. 9A illustrates a first validation user interface of the validationsystem configured for blind validation according to various embodimentsdescribed herein; and

FIG. 9B illustrates a second validation user interface of the validationsystem presenting scoring data for one or more groups according tovarious embodiments described herein.

DESCRIPTION

The present description describes various embodiments of a scoretracking and tournament management system, which may be referred toherein as a STTM system. The STTM system may include various systems,components, and modules configured to provide a lightweight platform forscore tracking and management of tournament data. Data collection may beunobtrusive to competing players, yet provide accurate, detailed dataregarding their game and performance. Management functionalities may beprovided on-site, off-site, or in a hybrid configuration. Pre-round andin-round tournament and score management functionalities may beautomated and employ customizable setup rules or profiles that areadaptable to a variety of tournament structures and that drasticallyreduce costs and personnel hours while also integrating multipletournament processes such as player grouping, tee times, scorecollection, location tracking, error correction, and score verification.The STTM system may be utilized to provide tournament scoring andorganization management and/or scoring system functionalities that maybe utilized to provide thorough data and feedback to players and otherinterested parties, in real time or delayed.

Although some embodiments of the STTM system described herein mayincorporate or utilize advanced infrastructure, the STTM system may beprovided in a widely applicable flexible package configured forportability that may utilize limited infrastructure with little impactto the amount, quality, and accuracy of the ultimate data product and/orthe tournament operational management support and functionalitiesobtained via its use. The flexible architecture of the STTM system maybe expandable, retractable, and/or modular to conform to availableinfrastructure and resources with only minimal variation in dataquality. For example, while various aspects of the STTM system aredescribed herein as providing integrated functions or operations, thesystems, components, and modules of the STTM system are not limited tocombined use. Indeed, the systems, components, and modules describedherein may be utilized separately or individually integrated with knownor future developed systems.

Operations described herein may be performed in association with one ormore electronic user devices. For example, computer readableinstructions may be stored in memory and when executed by a processorcause an user device to perform operations described herein. The memoryand/or processor may be local or remote with respect to the userdevices. User devices may include one or more tracking modules, one ormore companion devices 12, and/or one or more management devices. Userdevices may include suitable dedicated or multipurpose electroniccomputing devices and systems such as a mainframe, server, computer,dedicated device, desktop, laptop, tablet, smart device/phone, personaldata assistant. When utilized to collect live event data, the companiondevice will typically be a handheld tablet, smart device/phone, personaldata assistant, or dedicated handheld device.

The STTM system may include, incorporate, and/or communicate with userdevices that execute applications to perform the operations describedherein. The user devices may interface users with operations of the STTMsystem. For example, the user devices may be configured to access,execute, run, or emulate one or more STTM system applications and/orservices. The applications and services may be stored in local and/orremote memory and executed by local and/or remote processors. In someembodiments, applications, services, or the like are provided in wholeor in part in a cloud computing environment, e.g., SaaS, DCaaS, DaaS,PaaS, iPaaS, IaaS, or the like.

With reference to FIGS. 1 & 2 , a STTM system 10 may include a scoretracking system 20 configured to track location and/or competitionscoring, such as golf tournament scoring, and a management system 20 tomanage operations of the STTM system 10, which may include thecomponents thereof, such as devices and elements.

The STTM system 10 may include or incorporate various devices comprisingone or more of a tracking module 11, companion device 12, managementdevice 13, and/or location elements, such as a location network 14, orglobal satellite constellation infrastructure 15. The STTM system 10 mayinclude or incorporate a communication network 17 configured to transmitsystem data to, from, or among STTM system 10 components to perform theoperations of the STTM system 10 described herein. In variousembodiments, the communication network 17 may include or operativelynetwork one or more location elements.

Tracking modules 11 may comprise user devices configured to be carriedby a competing player or otherwise be located in close proximity to thecompeting player during play. Tracking modules 11 may include memoriesthat include instructions and processors that execute the instructionsfrom the memories to perform the various operations that are performedby the tracking modules 11. In certain embodiments, processors may behardware, software, or a combination thereof. In some embodiments,tracking modules 11 may also include interfaces 11 a (see, e.g., FIG.4C) that may enable a scorer, player, and/or other user to interact withvarious applications, such as a score tracking application, which may bereferred to as a ST application, and/or operations executed on thetracking modules 11, such as location signaling and/or locationcalculation processes, and to interact with the STTM system components,devices, systems, and/or elements thereof. In certain embodiments,tracking modules 11 may be and/or include a computer, any type ofsensor, a laptop, a set-top-box, a tablet device, a phablet, a server, amobile device, a smartphone, a smart watch, and/or any other type ofcomputing device, and/or any combination thereof. Tracking modules 11may be configured to perform various location operations. For example,tracking modules 11 may be configured to track their location and/orcommunicate locating information to the STTM system and/or locationelements. Tracking modules 11 may be configured for location trackingutilizing various technologies and location schemes described herein.For example, in some embodiments, a tracking module 11 is configured toobtain GPS coordinates corresponding to its location and transmit suchcoordinates to STTM system devices, or systems, such as the managementsystem 20, as described herein. In these or other embodiments, thetracking module 11 may operate as a beacon in a location network 14.Tracking modules 11 may be configured to communicate with variouslocation elements such as location networks 14 and/or location servicesto transmit data comprising location data, which may include locatingdata that may be utilized to determine location of the tracking modules11. The location data may also include a time stamp corresponding to thetime the location data relates. Tracking modules 11 may be configured tocommunicate data, such a location and/or locating data, over variouscommunication networks 17, such as a mesh network, a local network, acloud-computing network, an IMS network, a VoIP network, a securitynetwork, a VoLTE network, a wireless network, an Ethernet network, asatellite network, a broadband network, a cellular network, a privatenetwork, a cable network, the Internet, an intranet, an internetprotocol network, MPLS network, a content distribution network, shortrange wireless communication network, or any combination thereof.Tracking modules 11 may be configured to communicate directly withlocation elements, such as location networks 14, global satelliteconstellation infrastructures 15 via the various communication networks17 or indirectly via another STTM system device or network device. Forexample, in one embodiment, tracking modules 11 may directly transmitdata to STTM system 10 devices, elements, associated networks and/orlocation elements via one or more communication networks 17 and/orutilize a companion device 12 or management device 13 to transmitsignals to access various network-based, web-based, cloud-based, and/oronline services and content, such as those available on an internet, onother devices, and/or on various computing systems.

Companion devices 12 may be configured to communicate with, define,identify, and/or organize scoring data, which may include location data,associated with the tracking module 11. Additionally or alternatively,companion devices 12 may be utilized to collect and/or track othercompetition data. The companion device 12 may be utilized by a user toaccess data, content, services, and/or to perform a variety of othertasks and functions of the STTM system 10. As an example, the user mayutilize the companion device 12 to transmit signals to access variousweb-based, cloud-based, and/or online services and content, such asthose available on an internet, on other devices, and/or on variouscomputing systems. As another example, the companion device 12 may beutilized to access an application, such as the ST application, thatprovides one or more operative functions of the STTM system 10, such ascommunication with the management system one or more tracking modules11, one or more management devices, and/or one or more location elementscomprising one or more of a location network 14 and/or global satelliteconstellation infrastructures 15.

In certain embodiments, a companion device 12 may be used by a scorer tocontrol one or more operative functionalities of the STTM system 10. Thescorer may be a human such as a dedicated user or a player, a passiverobot, an active robot, a humanoid, a program, a computer, any type ofuser, or a combination thereof. The companion device 12 may include amemory that includes instructions, a processor that executes theinstructions from the memory to perform the various operations that areperformed by the companion device 12. In certain embodiments, theprocessor may be hardware, software, or a combination thereof. Thecompanion device 12 may also include an interface 12 a (e.g. screen,monitor, graphical user interface, etc.) that may enable the scorer tointeract with various applications, such as a ST application, executedon the companion device 12 and to interact with the STTM system 10, suchas with one or both of the score tracking system 20 or management system30. In certain embodiments, the companion device 12 may be and/or mayinclude a computer, any type of sensor, a laptop, a set-top-box, atablet device, a phablet, a server, a mobile device, a smartphone, asmart watch, and/or any other type of computing device. Illustratively,the companion device 12 is shown as a smartphone or tablet device inFIG. 1 .

Management devices 13 may be utilized by management users with respectto functions of the management system 30 to receive and transmit signalsto request various types of content, services, and data provided byand/or accessible by communications network 17 or any other networkthrough which the STTM system 10 communicates. In further embodiments,the management user may be a robot, a computer, a humanoid, an animal,any type of user, or any combination thereof. Management devices 13 mayinclude a memory that includes instructions, and a processor thatexecutes the instructions from the memory to perform the variousoperations that are performed by the management devices 13. In certainembodiments, the processor may be hardware, software, or a combinationthereof. Management devices 13 may also include an interface (e.g.screen, monitor, graphical user interface, etc.) that may enable theuser to interact with various applications (e.g., managementapplications) executing on the management device 13 and to interact withthe devices, elements, and systems of the STTM system 10. In certainembodiments, a management device 13 may be a computer, a laptop, aset-top-box, a tablet device, a phablet, a server, a mobile device, asmartphone, a smart watch, and/or any other type of computing device.Management devices 13 may be local or remote with respect to acompetition location. Management devices 13 may be cloud-based orweb-based.

In certain embodiments, the companion device 12, the tracking modules11, the management device 13, and/or location network 14 may have anynumber of software applications and/or application services storedand/or accessible thereon. For example, the companion device 12, thetracking modules 11, the management device 13, and/or location network14 may include applications for controlling the operative features andfunctionality of the STTM system 10 and/or score tracking system 20 ormanagement system thereof, applications for controlling any systemdevice, cloud-based applications, VoIP applications, cellularapplications, other types of phone-based applications, location and/orpositioning applications, media streaming applications, content-basedapplications, media-editing applications, database applications,internet-based applications, browser applications, mobile applications,service-based applications, productivity applications, videoapplications, any other type of applications, any types of applicationservices, or a combination thereof. In certain embodiments, the softwareapplications may support the functionality provided by the STTM system10, such as score tracking system 20 or management system 30 thereof,and methods described in the present disclosure. In certain embodiments,the software applications and services may include one or more graphicaluser interfaces so as to enable the users (e.g., scorers, players,system managers) to readily interact with the software applications. Thesoftware applications and services may also be utilized by the users tointeract with any device in the STTM system 10, any network of orutilized by the STTM system 10 (e.g., a location network or globalsatellite constellation infrastructure), or any combination thereof. Incertain embodiments, companion devices 12, tracking modules 11, and/ormanagement devices 13 may include associated device identifyingidentities, or any other identifiers to uniquely identify a particularcompanion device 12, tracking module 11, and/or management device 13.

The communications network 17 may be configured to link each of the STTMsystem devices, components, and elements and may include any number ofnetworks, which in one embodiment includes the location network 14. Forexample, the communications network may be utilized by the companiondevice 12 to connect with other devices within or outside communicationsnetwork 17. In various embodiments, the companion device 12, trackingmodule 11, management device 13, and/or location network 14 may belongto and/or form a portion of communications network 17. In certainembodiments, the communications network 17 may be a local, mesh, orother network that enables and/or facilitates various aspects of thefunctionality of the STTM system 10. In certain embodiments, thecommunications network 17 may be formed between or among various userdevices such as management devices 13, companion devices 12, trackingmodules 11, databases 18, or combination thereof, through the use of anytype of wireless or other protocol and/or technology. For example, userdevices may communicate with one another in the communications network17 by utilizing any protocol and/or wireless technology, satellite,fiber, or any combination thereof. Notably, the communications network17 may be configured to communicatively link with and/or communicatewith any other network of the STTM system 10 and/or outside the STTMsystem 10. In various embodiments, the tracking module 11 may beconfigured to communicate directly with one or more components of themanagement system 30 and/or location elements. The communicationsnetwork 17 may be configured to transmit, generate, and receive anyinformation and data traversing the STTM system 10. In certainembodiments, the communications network 17 may include any number ofservers, databases, or other componentry. The communications network 17may also include and be connected to a mesh network, a local network, acloud-computing network, an IMS network, a VoIP network, a securitynetwork, a VoLTE network, a wireless network, an Ethernet network, asatellite network, a broadband network, a cellular network, a privatenetwork, a cable network, the Internet, an intranet, an internetprotocol network, MPLS network, a content distribution network, shortrange wireless communication network, or any combination thereof.Illustratively, management devices 13 are shown as representativeservers and are shown as being included within or utilizing thecommunications network 171. As described above and elsewhere herein,management devices 13 will typically comprise a user interface enablinga user to perform scoring and/or tournament competition managementoperations described herein. In certain embodiments, the communicationsnetwork 17 may be part of a single autonomous system that is located ina particular geographic region, or be part of multiple autonomoussystems that span several geographic regions.

The functionality of the STTM system 10 may be supported and executed byusing any combination of the servers. The servers may reside incommunications network 17 or environment thereof, however, in certainembodiments, the servers may reside outside communications network 17.The servers may provide and serve as a server service that performs thevarious operations and functions provided by the STTM system 10. Incertain embodiments, the management devices 13 may comprise serversincluding one or more network servers, routers, gateways, switches,media distribution hubs, signal transfer points, service control points,service switching points, firewalls, routers, edge devices, nodes,computers, mobile devices, or any other suitable computing device, orany combination thereof.

The STTM system 10 may include or utilize a database 18 to store andrelay information that traverses the STTM system 10, cache content thattraverses the STTM system 10, store data about each of the devices inthe STTM system 10 and perform any other typical functions of a database18. Furthermore, the database 18 may include a processor and memory orbe connected to a processor and memory to perform the various operationsassociated with the database 18. In certain embodiments, the database 18may be connected to the servers, the companion device 12, the managementdevice 13, the tracking modules 11, any devices in the STTM system 10,any process of the STTM system 10, any program of the STTM system 10,any other device, system, element, any network, or any combinationthereof. The database 18 may comprise multiple databases 18. Databases18 may be local or remote. The database may be cloud-based.

The STTM system 10 may further include or transmit competition relateddata generated by the STTM system 10 to one or more data platforms 19.The data platforms 19 may comprise hardware, software, servers,computers, programs, applications, or the like configured to view,manipulate, analyze, store, or otherwise consume the generated data. Insome embodiments, data platforms 17 comprise competition data viewersand analyzing platforms available to players, coaches, administrators,fans, members of media organizations, broadcasters, or any other person.In a further embodiment, data platforms 17 comprise client platforms fordata consumption, and may include competition data views or analyzingplatforms. In the illustrated example, the data platforms 19 are shownas communicating via a web or cloud-based portion of the communicationnetwork 17. However, in various embodiments, the competition relateddata may be transmitted via other portions of the network, e.g.,locally.

While the present disclosure may reference particular applicationsexecuted on one or more electronic user devices, it is to be understoodthat such applications, including any application services, may beprovided within a single application, program, or platform or may bedivided, virtualized, distributed, or combined into or among any numberof executable platforms and resources.

The present description references various interface components.Interface components may include interface elements configured tointerface a user with an operation such as selection of a data value ordata element, display elements configured to interface a user with adisplay, data elements, or the like. Indicators, operators, options, andthe like described herein with respect to interfaces may includebuttons, toggles, switches, slide bar, swipe button/bar/field, sidebars,and or other interface elements. Such interface elements may beconfigured to be hard or soft. Similarly, interaction terminology suchas pressing, tapping, selecting, and the like may be performed with thehuman body, a stylus or other implement, a peripheral device such as amouse or keyboard, or other suitable user interaction.

With continued reference to FIG. 2 , the score tracking system 20 may beconfigured to track scoring with respect to play of a plurality ofcompeting players, such as golfers, competing in a competition. Thecompetition is described herein as a golf tournament, but those havingskill in the art will realize upon reading the present disclosure thatthe systems and methods described herein may be applied to othercompetitions and in other environments. Score tracking may also includetracking location of stroke events. As introduced above and described inmore detail below, the score tracking system 20 may include a trackingmodule 11 configured to be carried by or accompany a player. In someembodiments, e.g., as illustrated in FIG. 2 , the score tracking system20 may also include or be configured to incorporate a companion device12. The companion device 12 may be configured to receive score relatedinput, such as stroke event inputs, from a scorer and transmit the scorerelated data to the management system 30. The tracking module 11 may beconfigured with locating, positioning, and/or proximity technology, asintroduced above and described in more detail below, that may be used bythe tracking module 11 and/or another device, such as a companion device12, management device 13, location network 14, and/or location system 80to track the location of the tracking module 11. Using the companiondevice 12, a scorer may record events, such as stroke events, withrespect to play. Recordation of events may result in generation andrecordation of an associated time stamp and/or retrieval,identification, calculation, and/or transmission of location data fromthe tracking module 11 corresponding to a recorded event, e.g., when aplayer addresses or hits a ball. The location data or chronologicalsyncing of the time stamp with the location of tracking module 11 may beused by the location system 70 as a proxy for the location of theplayer's ball following the previous hit or the starting location of theplayer's ball prior to hitting the ball. A notable benefit of thepresent score tracking methodology is that a single scorer, which willtypically accompany a group of multiple golfers may record both scoreand location data in an unobtrusive manner. As described in more detailbelow, in various embodiments the tracking module 11 is configured to becompatible with a plurality of location service techniques, therebyproviding flexibility with respect to tracking the location of thetracking module 11, e.g., by utilizing available infrastructure withrespect to a course when necessary. The score tracking system 20 and/orthe STTM system 10 may include or incorporate location services such asone or more of a global satellite constellation infrastructure 15 orlocation network 14. The location network 14 will typically be a locallocation network with respect to a golf course the tournament is playedand may include radio receivers, transmitters, transceivers, antennas,UWB antennas, anchors, initiators, responders, cell towers, Wi-Fi accesspoints, beacons, geobeacons, BLE gateways, or the like. In someembodiments, a location network 14 including external location/signalnetworks that utilize short range or long range location technologies,which may include signals of opportunity.

In various embodiments, the tracking module 11 is configured to be incommunication with the companion device 12 and operable to retrievecalculated location data or location signaling parameters from thetracking module 11 that may be used by the companion device 12,management device 13, and/or location system to calculate the locationof the tracking module 11 at a given time, time range, or continuously.However, in some embodiments, the tracking module 11 may not be incommunication with the companion device 12 with respect to locationtracking operations, e.g., another device may calculate or receive thelocation of the tracking module 11. For example, time stamps set by thecompanion device 12 may be transmitted to another device forchronological pairing with the location of the tracking model 11 beforeor after transmission of the same to a management device 13 or themanagement device 13 may be in communication with the tracking module 11and companion device 12 to receive the location data for pairing withthe time stamp.

In one example, the tracking module 11 obtains its GPS coordinates viacommunication with global satellite constellation infrastructure 15 andtransmits the coordinates to the management system 30. The companiondevice 12 may also transmit stroke events including associate timestamps to the management system 30. The location system 80 may then pairtime stamps with corresponding location coordinates.

In one example, the tracking module 11 obtains its location, which mayinclude location coordinates, via location signaling with a locationnetwork 14, such as a UWB or other location network described herein orsimilar. In one configuration, the tracking module 11 calculates itslocation as described herein and transmits the location to themanagement system 30. In another configuration, the location network 14calculates the location of the tracking module 11 and transmits thelocation to the management system 30 or the companion device 12, whichsubsequently transmits the location and/or the location paired withcorresponding time stamps to the management system 30. The companiondevice 12 may also transmit stroke events including associated timestamps to the management system 30. The location system 80 may then pairtime stamps with corresponding location coordinates.

In one embodiment, the management system 30 includes a device managementsystem 40 configured to manage a plurality of tracking modules 11 andassign the same to players. The device management system 40 may beexecuted on one or more management devices 13. In one configuration, thedevice management system 40 communicates with the tracking modules 11during play to track locations of the tracking module 11. When thecompanion device 12 sets a time stamp with respect to a location of thetracking module 11 relative to an assigned player, the device managementsystem 40 receives the time stamp and pairs it with the location of thetracking module 11 at the time set by the time stamp. This locationinformation may be provided to the data management system 40 for reviewand/or made available for transmission or use by STTM system operationsor data platforms 19. As noted above and elsewhere herein, locationcalculation and/or pairing of location coordinates with time stamps maybe performed by the location system and made available to other systemsof the management system 30 or the functionalities of the locationsystem 80 may be provided by other systems of the management system 30.The location calculation may be perceptually instantaneous or otherwisein real time. In one embodiment, the companion device 12, trackingmodule 11, management device 13, location network 14, and/or locationsystem 80 may continuously or near continuously track the location ofthe tracking module 11. Such continuous or near continuous tracking maybe used to address location tracking/network latency. For example, whena scorer records a stroke event that causes setting of a time stamp atthe time the ball is hit, in nearly all instances, the most recentcalculated location within five seconds of the time stamp will providean accurate location of the ball when hit. In one embodiment, the scorerwill set the time stamp for location purposes at address.

In various embodiments, the management system 30 includes one or more ofa round management system 60 configured to manage rounds and groupingsfor players that are playing in an event, a data management system 60configured to review and edit scoring data recorded by the scoretracking system 20, or a validation system 70 configured to providestreamlined validation of a player's official scorecard against scorescollected by the score tracking system 20. In the above or anotherembodiment, the management system 30 may include a location system 80.The location system 80 may be configured to handle tracking module 11location data, calculation of location data from locating data, pairtime stamps with location data, make zone determinations, and/or comparezone determinations with scoring data zone identification. In oneembodiment, the companion device 12 may transmit scoring data to themanagement system 30. The tracking module may also directly orindirectly transmit location data or locating data to the managementsystem 30. Stroke events and corresponding time stamps may be availableto the location system for pairing with tracking module locations. Thelocation system 80 may share data and/or functionalities with thevarious systems of the management system 30. For example, devicemanagement system and/or data management system may execute or accessone or more of the above location determination functions, instead of orin addition to the location system 80. In various embodiments, thelocation system 80 includes or communicates with one or more locationnetworks. As described in more detail herein, location networks mayinclude GPS, Wi-Fi, RFID, BLE, UWB, NFC, cellular, etc.

As introduced above, a companion device 12 may be configured to executeor run the ST application. The ST application may comprise a mobile app,web app, cloud-based, or other application format and includeinstructions operable to perform the score collection features describedherein with respect to the companion device 12. When the companiondevice 11 is configured to communicate with the tracking module 11, theST application may be configured to provide communication protocolsbetween the companion device 12 and the tracking module 11. For example,the ST application may configure the companion device 12 to communicatewith the tracking module 11, provide updates, receive data for storage,provide processing operations, transmit alarm initiation instructions,obtain battery life or charge status, receive tracking module 11location data, initiate a location data event, relay data received fromthe tracking module 11 to a storage or another computing device, performproxy services for the tracking module 11, or other operations describedherein. Additionally or alternatively, the ST application may configurethe companion device 12 for communication with management devices 13 ofthe management system 30. For example, the ST application may beconfigured to receive and incorporate groupings assignments, roundinformation, tee times, or the like from the round management system 60.In the above or another example, the ST application may be configured toreceive player and tracking module 11 assignments from the devicemanagement system 40, incorporate the player and tracking module 11assignments into collected scoring data (stroke event data, locationdata, time stamps, club selection, etc.), transmit stroke event dataincluding associated time stamps to the STTM system 10, e.g., locationsystem 80, device management system 40, data management system 50,and/or validation system 70, and/or communicate with tracking modules 11to pair the tracking modules 11 with the assigned players. In someembodiments, however, assignments may be retained by the managementsystem 30 and the companion device 12 may accompany stroke event timestamps or location data with identifiers of respective tracking modules11 from which the management system 30, e.g., data management system 60or location system 80, uses to pair the location of the tracking module11 at the time stamp with the player assigned to the tracking module 11.In an above or another embodiment, the ST application may be configuredto transmit collected scoring data recorded by the companion device 12to the management system 30, e.g., data management system 60, validationsystem 70, and/or location system 80.

In one embodiment, the tracking module 11 comprises a compact housingthat may be easily carried or worn by an individual. FIGS. 4A-4D provideviews of example tracking modules 11. While larger tracking modules 11may be used, in the illustrated examples, the tracking modules 11 areprovided with a housing 110 generally smaller than a deck of cards. Inone example, the housing 110 may be fitted with a clip for clipping to abelt, pocket, or other surface. In one embodiment, a wearable receptaclefor receiving the tracking module 11 may be provided that may be carriedor worn by an individual. In one example, the receptacle may include aclip for clipping to a belt or pocket or may include or attach to awearable band. Numerous variations may be implemented. For example, thetracking module 11 may be integrated or imbedded in a clothing article,such as a belt, belt buckle, hat, or bracelet. In some embodiments, thetracking module 11 may be integrated in a tablet, laptop, smart device,such as a phone or PDA, or other portable electronic device. In variousembodiments, the housing 110 may be configured to be opened formaintenance, part replacement, upgrades, or other desired purpose. Forexample, the housing 110 may include a removable panel or comprise aclamshell design. In one embodiment, the housing 110 may be waterproofor water resistant with respect to the interior of the housing 110. Forexample, a panel or clamshell may seat on a gasket

FIG. 4D is a semi-schematic of an interior of a tracking module 11illustrating components that may be included in various embodiments of atracking module 11. In some embodiments, the tracking module 11 includesa wired data communication port 111. The port 111 may be provided oraccessible from an exterior of the housing 110 or may be accessible byremoval of a panel or clamshell thereof. The wired data communicationport 111 may be utilized for programming, downloading, or other datacommunication needs as an alternative or backup to wireless datacommunication.

The tracking module 11 may include one or more batteries 113 configuredto provide power for the tracking module 11 operations. Various standardand custom sized batteries 113 may be used, such as AA, CR123A, 23A, orcoin cell such as CR2032. While a compact size is preferred, largerbatteries 113 may also be used. In one example, a user may wear orotherwise carry a separate battery pack or power source that powers thetracking module 11, either by wired or wireless connection. Any suitabletype of battery 113 may be used that is sufficient to power the trackingmodule 11. For example, batteries 113 may include lithium, alkaline,silver oxide, carbon zinc, zinc air, lithium ion, NiCD, or NiMH. Varioustracking modules 11 configurations may include or be configured tooperate with rechargeable batteries 113, such lithium ion, NiCD, orNiMH. In one embodiment, the tracking module 11 includes a battery 113that is rechargeable, such as a rechargeable lithium polymer 2300 mAhbattery.

Some configurations of the tracking module 11 may include a chargingport 112 operable to receive a supply of power to charge the battery113. The charging port 112 may include a female or male connector. Theport 112 may be configured to be waterproof or water resistant toprevent water from entering the charging port 112. For example, thecharging port 112 may be separated from the interior of the housing by agasket. In a further example, access to the charging port 112 isprovided by removing a panel seated on a gasket or by inserting anexternal charging interface connector through a slit in a water barriermaterial. In another example, a removable plug may be seated within orover the charging port interface to prevent water intrusion. In oneembodiment, the tracking module 11 is configured to be chargedwirelessly. In one embodiment, the tracking module 11 is configured witha charging port to recharge batteries while in the housing. For example,the housing may include a wired or wireless charging port. A magneticwireless charging port, USB (e.g., A, B, Mini A/B, Micro A/B, C),Thunderbolt, DC power connectors, or other suitable power deliveryinterface technology may be used. Custom charging interfaces may also beused. In some embodiments, a charging port 112 is configured tosimilarly be operable for use as a wired data communication port 111. Inone embodiment, the charging port 112 comprises a USB C connection. Inthe above or another example, the housing may be equipped with acharging interface configured to be plugged into a charger having aplurality of charging ports for bulk charging of multiple trackingmodules 11.

In various embodiments, the tracking module 11 may be configured with awireless communication port 114 comprising one or more wirelessreceivers, transmitters, and/or transceivers. The wireless communicationport 114 may be configured to transmit and/or receive wireless datacommunications, e.g., signals, via any wireless communication medium orprotocol, such as those including or incorporating radio waves,cellular, WiFi, short-range wireless, Bluetooth, or other suitablewireless communication technology. The wireless communication port 114may be configured for multiband operation. For example, the wirelesscommunication port 114 may be configured for communication in multiplefrequency bands. The multiple frequency bands may include cellularnetworks (4G, LTE-M, NBIot, 2G, etc.) and/or other frequency bands. Thewireless communication port 114 may be configured to transmit and/orreceive data, such as location and/or locating data, from a locationnetwork, global satellite constellation infrastructure, or the like. Thewireless communication port 114 may be configured to transmit and/orreceive locating data such as parameters for calculation of location.The wireless communication port 114 may be configured to operate as abeacon as described in more detail below. The tracking module 11 may beconfigured with a location alarm. The location alarm may be wirelesslyactivated remotely via wireless communication from one or more of aremote command center, management device, or companion device equippedwith a suitable wired or wireless transmitter or transceiver fortransmitting the alarm activation signal to the wireless communicationport 114 of the tracking module 11, which may include communicationthrough intermediate wired networks of a communication network. Forexample, the alarm activation signal may be transmitted and/or receivedvia Wi-Fi, cellular, short-range wireless, Bluetooth, or other suitablewireless communication technology.

In one embodiment, a companion device of a management device, such as amanagement device of the device management system, may be configured,e.g., via an application, to transmit the alarm activation signal thatwhen received by the wireless communication port 114 of the trackingmodule 11, causes the tracking module 11 to output an alarm. The alarmmay include activation of vibration device, such as an ERM motor or LRA,may be housed in the housing and operable to produce vibration inresponse to receipt of the alarm signal. Additionally or alternatively,the alarm signal may trigger an audible alarm to be output from aspeaker 116 or other noise producing device within or associated withthe housing. Additionally or alternatively, the alarm signal may triggeractivation of lights, such as LEDs, or activation of an LCD or otherlighted display.

The tracking module 11 may include memory 119 a and a processor 119 b toexecute instructions stored in the memory 119 a or otherwise received toperform the operations of the tracking module 11. In some configurationsthe housing 110 includes a memory expansion port or slot for connectingto additional memory storage. The expansion slot may be configured tohouse an expansion memory device, such as a micro SD card or the like,or receive a plug for a wired connection to an expansion memory device.The memory 119 a may be used to store collected data such as locationand time data. Such data may be transmitted to a storage device,receiving device, processing device continuously, periodically, daily,or upon request.

The tracking module 11 may be equipped with an accelerometer 1100. Theaccelerometer 1100 may be utilized for movement detection. Movementdetection may be utilized in conjunction with positioning and locationtracking, determination, or acquisition, e.g., movement detection mayinitiate transmission of location signals and/or listening for the same.Movement detection may initiate transmission of tracked, determined, oracquired location or position data, e.g., to a companion device,location network, or STTM system device. In some embodiments, theaccelerometer 1100 may be configured for movement detection with respectto detecting a swing by the player. Detection of movement correspondingto a swing may be used in addition to or instead of scorer entry of aswing or “shot hit” as described below. The accelerometer 1100 maysimilarly be configured to detect address, e.g., corresponding to a timeperiod with a pause in movement before detection of movementcorresponding to a swing.

The tracking module 11 may include a user interface 11 a for interfacingoperations and/or states with a user. In various embodiments, the userinterface 11 a includes a display 118 for displaying information. Anysuitable display 118 may be used, such as an OLED screen. Theinformation may include battery capacity, battery life or state, anoperational mode, such as awake, asleep, ready to receive instructions,operating, or the like. In some embodiments, the display 118 may presentdata with respect to a current operation or assignment. For example, thedisplay may be configured to display a group number and/or player towhich the tracking module 11 is assigned with respect to datacollection.

In one embodiment, the user interface 11 a includes one or moreindicator lights. The indicator lights may be used to indicate anoperation state, such as powered, processing data, uploading data,downloading data such as instructions, assignments, or updates,receiving and/or acquiring location/position data, receipt ofinstructions, transmitting data, operation underway, operation complete,or the like.

In one embodiment, the tracking module 11 includes a speaker 116operable to output sound. The speaker 116 may be used to output audiblealarms for locating purposes, battery life, confirmation of receipt of auser interaction or a communication, initiation of wake-up and/or sleepmodes, communication of instructions received from a companion device12, or other desired use.

In various embodiments, as introduced above, the tracking module 11 isequipped with locating, positioning, and/or proximity technology toassist in locating a misplaced tracking module 11 and/or determiningprecision location of the tracking module 11. For example, the trackingmodule 11 may be configured to output locating signals, such as packets,blinks, requests, response, etc., directionally or omni directionally,that may be used by a companion device, location network, managementsystem, and/or location system to locate and/or determine thelocation/position of the tracking module 11, e.g., based on signalstrength, signal parameters, and/or signal characteristics. Additionallyor alternatively, the STTM system, which may include location elementsdescribed herein, may be configured to locate a tracking module 11utilizing other techniques, such as those described below.

The STTM system or score tracking system thereof may comprise a locationnetwork configured to provide location tracking functionalities and/orservices. The location tracking network (see FIG. 2 ) may include aplurality of location signaling devices. Location signaling devices mayinclude receivers, transmitters, transceivers, gateways, beacons, UWBantennas, anchors, initiators, responders, real time kinematic (RTK)base stations, or the like setup for outdoor location/positiondetermination. The location signaling devices may be configured toutilize radio waves such as UHF, NFC, Wi-Fi, Bluetooth Low-Energy,and/or UWB. The location signaling devices may be positioned around acourse of play and be configured to communicate location signals with aplurality of tracking modules 11. The location network may be configuredfor device-side location calculation and/or network-side locationcalculation. The location network and/or tracking module 11 may utilizevarious localization techniques such as RSSI, RSSI-fingerprinting,and/or time of flight (ToF), time difference on arrival (TDPA), and/orangle of arrival (AoA).

The tracking module 11 may include one or more short range communicationdevices, such as WiFi, Bluetooth, BLE, NFC, and/or Ultra-Wide Band chipsconfigured to provide short range location signaling, locationsearching, proximity determination, and/or ranging. FIG. 4D illustratesa wireless communication port 115 configured for ultra-wide band, butother short range communication protocols and/or signaling may beutilized. Wireless communication port 115 may be in addition to orinstead of wireless communication port 114. In some embodiments,wireless communication port 115 comprises a Wi-Fi chip, BLE chip, LTEchip, and an ultra-wide band chip and wireless communication port 114comprises a cellular chip. Depending on the configuration, a locatingservice may be utilized by the tracking module 11, STTM system, locationsignaling devices of a the location network, and/or any device suitablyconfigured to receive the location or locating signal and utilize thesignal and associated data to locate and/or determine aposition/location of the tracking module 11.

Additionally or alternatively, the tracking module 11 may be configuredto receive locating signals from location signaling devices that may beused to determine the location/position of the tracking module 11,either by the tracking module 11, companion device, location network,location system, or otherwise. Beacons signals, for example, may be usedto determine the location/position of the tracking module 11. Asintroduced above, the locating signal may be output via short rangecommunication technology. In various embodiments, locating signals maybe transmitted via radio waves such as UHF, NFC, Wi-Fi, BluetoothLow-Energy, or Ultra-Wide Band. For instance, the tracking module 11 maybe configured to receive locating signals, e.g., beacon packets or UWBanchors. In a device-side use case, the tracking module 11 may calculateits location using received location signals or relay the locationsignals/packet data and/or associated receipt parameters to anotherdevice, such as a companion device or management device, for directprocessing or indirect processing, e.g., by utilization of an API. Forexample, if beacons are present, the tracking module 11 may receivebeacon packets which the tracking module 11 or a companion device ormanagement device in communication with the tracking module 11 may usefor location/position determination, e.g., via RSSI,RSSI-fingerprinting, and/or ToF techniques. In a network-side locationcalculation use case, the tracking module 11 may continuously outputsignals, transmit locating response signals to locating signals receivedfrom location signaling devices, transmit poll signals, or the likewhich the location network or other STTM system component, such as thelocation system, may use to calculate location of the tracking module11, e.g., via TDPA, ToF, and/or AoA. In one embodiment, the locationnetwork includes a plurality of location signaling devices, e.g.,beacons or anchors, positioned around an area of play, such as a green,fairway, rough, and/or tee box. The tracking module 11 may receivetransmitted signals for position/location determination. In a furtherexample, the tracking module 11 may transmit response locating signals.In an above or another example, three or more beacons or anchors may beused, e.g., around a green, for precision and accuracy.

In one embodiment, the tracking module 11 may be configured for UWBlocation/position determination in conjunction with the locationnetwork. For example, the tracking module 11 may include multipleantennas for direct or indirect utilization of AoA/phase difference. Thetracking module 11 may be configured for single-sided, two-sided, ormulti-sided ranging as an initiator and/or responder. The trackingmodule 11 may be configured to operate as an initiator in a timedifference of arrival model with synchronized anchors of the locationtracking network positioned around a golf course for precision locationand accuracy, e.g., down to 1 cm. In one embodiment, multiplepositioning technologies may be utilized to enhance positioning such asWi-Fi, BLE, and/or UWB. In further embodiments, one or more of thesepositioning technologies may be utilized in conjunction with one or moreglobal satellite constellations. In some embodiments, the locationsystem includes a UWB positioning system including a plurality ofanchors that receive locating signals from the tracking module 11. Theanchors may utilize time difference of arrival (TDoA) or other suitabletechnique to determine the coordinates of the tracking module 11. Itwill be appreciated that in such a network or any other locationnetwork, the location system may receive and/or collect the locatingdata or location data. The location system may calculate location fromthe locating data. The location system may further comprise all or aportion of the location network.

The tracking module 11 may be configured to utilize one or more globalsatellite constellations for accurate location determination andposition. Illustratively, FIG. 4D shows inclusion of a GPS chip orreceiver 117 configured to receive GPS location coordinate data. Whilethe present description generally refers to GPS, those having skill inthe art will appreciate that such reference applies equally to otherGlobal Navigation Satellite Systems (GNSS), such as GLONASS, BeiDou,Galileo, or other current or future GNSS. GPS location may be augmentedwith WAAS (Wide Area Augmentation System), Differential GPS (DGPS),e.g., Global Differential GPS (GDGPS), real time kinematic (RTK),Continuously Operating Reference Stations (CORS), Signals of Opportunity(SOP)-based or augmented navigation, UWB, LTE, cellular, radio,television, Wi-Fi, other satellite signals, or the like. In someembodiments, the location network may be used instead of or in a hybridmanner with one or more global constellation coordinate systems. Thelocation network may utilize location signals and methodologiesincluding but not limited to RTK, CORS, SOP-based, UWB, LTE, cellular,radio, or Wi-Fi. In one example, the tracking module 11 is configured toutilize any or all of the available global satellite constellations(GPS, GLONASS, BEIDOU, GALILEO & QZSS) for accurate positioning 0.5-5 mtyp. accuracy outdoors or better. In one embodiment, the tracking module11 transmits its coordinate location to the management system over acellular network.

In one embodiment, the communication network includes a LPWAN (Low PowerWide Area Network) through which the tracking module 11 transmitslocation data directly or indirectly to the management system. In oneexample, the LPWAN includes a LoRa network. The companion device maysimilarly transmit stroke event data over such a network. Unlike currentscore tracking methodologies, the configuration of the present scoretracking system may utilize low data loads suitable for small datapacket transmission over low power, long range networks, while stillmaintaining a robust volume of accurate data.

As introduced above, the STTM system may utilize a UWBpositioning/location network for all or a portion of location services.GPS or other location services may also be used at the same time, in ahybrid configuration, or as a separately selectable option or settingwith respect to the system devices.

In various embodiments, the tracking module 11 may be configured tocontinuously output a location or locating signal or may be configuredto output the location signal upon receipt of an instruction to do so.For example, an ST application or location tracking network may beoperable to address one or multiple tracking modules 11 to initiateoutput of the location signal. In one embodiment, tracking modules 11are configured to determine location coordinates every n seconds andtransmit all or a portion of the coordinates every n+x seconds. Forexample, a tracking module 11 may be configured to collect locationcoordinates at any predetermined time interval and transmit collectedlocation coordinates at any time interval.

In one embodiment, a tournament course and/or surrounding grounds may bemapped and divided into geolocation zones. Location data, which mayinclude locating data, of a tracking module 11 may be transmitted to themanagement system, e.g., to a management device, for determination of acurrent geolocation zone corresponding to the location of the trackingmodule. The current zone may be transmitted to the tracking module 11,which may trigger an action by the tracking module. In one embodiment,the tracking module 11 is programmed to identify the current zone andidentification of the current zone may trigger an action. In someembodiments, the tracking module 11 may transmit coordinates to amanagement device that passes the coordinates through an API includinggeolocation zones and returns the current zone of the coordinatecorresponding to the tracking module. Actions that may be triggeredinclude alerts, API calls, database entries, alarms, etc. based onentering, exiting, or being in a particular zone.

FIG. 3 illustrates an example geolocation zoning of a golf hole. Thezones include a green zone 31, fringe zone 32, fairway zone 33, firstcut zone 34, hazard zone 35, rough zone 36, natural area zone 37, andtee box zone 38. Each zone includes the coordinates corresponding to therespective zone. As noted above, other or additional zones may beincluded. In various embodiments, all holes are zoned. As introducedabove and described in more detail below, geolocation zoning may be usedfor various operations of the STTM system. For example, the companiondevice, score tracking system, or management system may mark or record agroup of players as being on the green when the tracking module assignedto the first player in the group crosses into the green zone 31. Asnoted above, the location system may collect or receive location datawith respect to the tracking modules. The location system may use thislocation data to determine a location of the tracking module. Thelocation coordinates may be applied to predefined coordinate rangescorresponding to defined zones to determine which zone the trackingmodule is currently located. This zone determination may be performed inreal time, e.g., within less than 10 seconds or 5 seconds or less. Thelocation system may utilize a most recent set of location coordinates orintervals of location coordinates to determine a current location and/orzone in which each tracking module 11 is located to track location ofthe tracking modules 11. Similarly, the group may be marked or recordedas completing a hole when the tracking module assigned to the lastplayer in the group crosses out of the green zone 31 after the group ismarked or recorded to be in the green zone 31. When the tracking module11 assigned to the first player to cross into the tee box zone 38 isdetected, the group may be marked or recorded as being in the tee box.As described in more detail below, the user entries into the STapplication on the companion device may additionally or alternately beused to mark or record locations. In one embodiment, a group marked orrecorded as in the tee box, may advance the ST application to the holeassociated with the tee box. In another embodiment, a scorer entering,into the companion device, “in the hole” with respect to the last playerin a group to hole out a hole, automatically advances the ST applicationto the next hole. In another embodiment, the ST application will notadvance to the next hole until “in the hole” is entered for all playerson a preceding hole and a player enters the tee box of the hole.

As introduced above, tracking modules 11 may be configured to collectlocation coordinates at any predetermined time interval and transmitcollected location coordinates at any time interval. In one example, thetracking module may be configured to obtain location coordinates, e.g.,GPS location, every second and transmit the obtained locationcoordinates to the location system every five seconds. However, thetracking module 11 may be configured to collect location data andtransmit collected location data at any desired time intervals.

In one embodiment, the location of the tracking module 11 iscontinuously tracked, e.g., at one second intervals, or as otherwiseprogrammed. In one embodiment, pairing time stamps with location mayanalyze location coordinates collected prior to and after the timecorresponding with the time stamp to identify the most likely location.

As described in more detail below, the scorer using the companiondevice, may also enter ball locations or “from location.” Such locationsmay correspond to defined zones of the hole. Using the zonedetermination from the tracking module coordinates, the location systemmay compare the determined zone with an input zone and identify thepresence of any inconsistencies. For example, the determined zone may befairway but the input zone may be bunker or hazard. In this situation,the location system may be configured to accept the zone location asbunker or hazard. In one embodiment, the location coordinate may beadjusted to the bunker or hazard. In another embodiment, the locationcoordinate may be retained and only the zone location corresponding tothe “from location” is changed to correspond to that entered by thescorer.

The companion device may record time stamps at address and/or shot hit.The location network may apply an algorithm that analyzes locationsprior to and after the time stamp. The lookback and forward time periodsmay be adjustable in the location system. As an example, the lookbackand forward time periods may be 30 seconds. In one embodiment, thelookback period may be longer than the forward period. The locationsystem may look to the locations most proximate in time to the timestamp and identify the most accurate. Identification of the mostaccurate location may include determination of a period of time of 5 to10 seconds or longer with little to no change in location. As describedabove, the tracking module may be able to detect when a swing is made.Such data may be provided to the location system to confirm or enhancethe analysis with respect to the time stamp. For example, the locationsystem may pair the location at the time of the swing andcross-reference the location with the location obtained by the scorerprovided in the time stamp. In some embodiments, if the location is notknown or does not correlate with an expected location, e.g., coordinatescorrespond to a different hole, the location is not recorded.

In one embodiment, tracking modules 11 are configured with operationwindows. For example, location data, which may include locating data,will not be stored or transmitted outside of the defined time of theoperation window. Such an operation window may be registered to eachtracking module 11. In this or another example, location data orlocating data will not be stored or transmitted if the tracking module11 is not registered to a player in the tournament. In any of the aboveor another example, the tracking module 11 may not transmit locationdata or locating data if the coordinates obtained are not coordinates ofthe course(s) hosting the tournament. Thus, in some embodiments, thetracking module 11 may be programmed with allowable coordinatesassociated with the tournament. Such a limitation may enhance privacy tousers of the tracking module 11. In some embodiments, operation windowregistration, player registration, and/or coordinate limitations may beoverridden by the STTM System 10, e.g., to locate a lost or missingtracking module 11.

In one embodiment, the STTM System 10 may be configured to pass anotification to a tracking module 11 registered to a player that is outof position or playing too slowly. For example, the tracking module 11may output a text notification (if so equipped), audible and/or visualalarm, or vibration. Additionally or alternatively, a companion deviceassigned to a group including a player that is out of position orplaying too slowly may receive such a notification via the STapplication. In a further example, the notification may includeinstructions with respect to how to correct the problem, e.g., arrive ata particular location at or by a time or ask player to increase pace.

As introduced above, and with particular reference to FIGS. 5A-5C, theSTTM system may include a device management system 40 configured toassign tracking modules 11 to players. The device management system 40may provide device managers data and/or device access to devicemanagement operations locally, remotely, and/or from any location viamanagement devices. In some configurations, the device management system40 is configured to assign Tracking modules to a group which, in turn,will be assigned to a player. The tracking modules may be activelyassigned to a player, e.g., a software of the tracking module may beprogrammed, typically temporarily, to a player such that location data,locating data, or other data transmitted from the tracking moduleincludes identification of the assigned player. The location data mayinclude a time stamp corresponding to the time the location data wascollected or otherwise relates with respect to the location of thetracking module. In some embodiments, the tracking module is playeragnostic and an identification number or other unique identifierassociated with the tracking module is established in the STTM systemsuch that communications from the tracking module pair the identifierwith the assigned player. In various embodiments, whether programmed oragnostic, the companion device may be configured to associate thetracking module with an assigned player. For example, the ST applicationmay be programmed by the device management system or by the scorer toassociate the tracking module with the assigned player for display onthe companion device. In some embodiments, the companion device maytransmit tracking module identifiers and/or player names to the STTMsystem, such as location system, device management system 40, datamanagement system, or validation system, when a stroke event associatedwith a location time stamp is input.

The device management system 40 may be configured to import and grouptracking modules for tournament operation. In one example, the devicemanagement system 40 may be configured to store and/or present trackingmodule management data. In certain embodiments, the device managementsystem 40 is configured to load or import new tracking modules andcreate new devices. Importation of new tracking modules may includeuploading a file, such as a CSV file, including tracking module profilesor a list of tracking module profiles to manage. Tracking moduleprofiles may include specific tracking module management data such asidentifiers and/or other tracking module data. The device managementsystem 40 may be configured to store the tracking module profiles to alocation and save the associated tracking modules loaded and thelocation of the tracking modules. The device management system 40 may beconfigured to directly or indirectly receive specific device relatedmanagement data from the loaded tracking modules and present at least aportion of this data on a user interface display. FIGS. 5A-5B illustrateembodiments of a user interface that present device management data andenables users to perform device management operations.

FIG. 5A provides a device management overview presentation 400 includinga device listing 401 of the tracking modules and their associatedlocations 402 that are loaded into the device management system 40according to various embodiments. The device management system 40 isconfigured to enable a user to create a location and delete a location.In one embodiment, when a user deletes a location, a warning prompt maybe generated to notify the user of the deletion upon user confirmation.Locations 402 may be locations associated with the listed trackingmodules. A location 402 may reference a geographic location bycoordinate, landmark, or location reference (e.g., 9 th hole, volunteermeeting area, gear locker, equipment room, geolocation zone, etc.).Additionally or alternatively, a location 402 may refer to a physicalcontainer that contains the respective tracking modules (e.g., container681). In one example, locations 402 refer to containers comprisingcontainment devices configured to function as charging stations tocharge tracking modules and/or storage stations for storing trackingmodules. In one example, locations 402 refer to a physical containercontaining the tracking modules as well as a geographic location of thecontainer, which may be a coordinate, a geolocation determined zonecorresponding to the listed tracking modules, or a location that isdefined by the device management system 40. The locations 402 anddevices included in the device listing 401 may be imported into thedevice management system 40 prior to assignment. In one configuration,the number of devices per location may be pre-defined in the devicemanagement system 40 at importation.

FIG. 5B illustrates an example user interface 403 generated by thedevice management system 40 to provide tracking module managementfunctionalities and present device management data for loaded trackingmodules. The data elements included in tracking module device managementdata or profiles shown in the illustrated embodiment include (a)functioning 404, (b) device name 405, (c) device ID 406, (d) accuracy407, (e) position 408, (f) signal strength 409, and (g) battery life 410for each tracking module. In other embodiments, fewer or additionaldevice data elements may be presented. A location element 411, which maycorrespond to the location 402 provided in the overview presentation400, may be provided at the top of the hierarchy. The loaded and storedtracking modules and associated device data elements may be stored tothe identified location 411 and may be presented underneath the location411 element. In one configuration, the device management system 40 maybe configured to enable a user to move locations and associated devicemanagement data to change the order in the presentation. In the above oranother configuration, a user may be able to collapse and expand thetracking module data for selected locations, e.g., by interacting withthe location 411 field. In an above or another configuration, thepresentation includes a location labeled “storage” 412 that storesloaded but currently unused tracking modules. In one example, thislocation label is fixed and cannot be deleted. As noted above, thedevice management system 40 may be in direct or indirect communicationwith loaded tracking modules to receive data associated with one or moredevice data elements. In various embodiments, the presentation may beconfigured to auto refresh at predetermined time intervals, such asevery 30 seconds, or upon the occurrence of an event, such as a devicedata element being received outside a predetermined acceptable range orbeyond a threshold value. In one configuration, the presentation mayinclude a manual refresh option to cause the presentation to immediatelyupdate the values of the device data elements.

If a respective tracking module is sending location signals, e.g., GPSinformation/coordinates, poll signals, response signals, location signalparameters, location data, locating signals, etc., “functioning” isidentified in the functioning 404 data element.

Device name 405 may be a unique name associated with the device. DeviceID 406 may be an assigned manufacture ID number of the GPS or otherlocation technology. Accuracy 407 may refer to a measured accuracy ofthe device's location as a distance. Position 408 may refer to thecurrent location of the device. Depending on configuration and locationtechnique(s) being used, the position value may be provided inlatitude/longitude, grid coordinates, or other suitable positioncoordinate designation. In various embodiments, the device managementsystem 40 may perform one or more location operations associated withthe location system. For example, the device management system 40 mayreceive transmitted location data from tracking modules during play. Thedevice management system 40 may provide such location data to thelocation system continuously, upon request, or at predeterminedintervals. In one example, the location system receives time stamps fromthe ST application corresponding to location events entered into acompanion device. The location system may provide the time stamps to thedevice management system 40 for pairing with the corresponding locationof a specified tracking module at the time stamp. In another example,companion devices may transmit location events to the device managementsystem 40 for location pairing. Any suitable data handling and flow maybe used to perform such location operations during play. For example,tracking modules may transmit location and/or locating data to thelocation system and companion devices may transmit location events tothe location system for time stamp and tracking module location pairing.

Signal strength 409 may be the current signal strength of the locationsignals received by and/or transmitted by the respective trackingmodule. For example, signal strength 409 may refer to a wireless signalstrength, such as cell, Wi-Fi, UWB, etc., and may be queried by thedevice management system 40 to measure the health of the tracking modulewith respect to its ability to share location or other data, such asswing. In one embodiment, signal strength 409 may refer to accuracy forlocation based coordinates. Battery life 410 may provide a value relatedto life of a battery of the tracking module. For example, a battery lifeelement data value may be presented as a percentage of battery liferemaining or a time or time period when the battery will be fullydepleted or depleted to a threshold level

In some embodiments, communication between the device management system40 and tracking modules may be two-way. For example, the devicemanagement system 40 may be configured to address tracking modules. Inone such configuration, removing or transferring a tracking module froma location 402/411 via operation of the device management system 40 maycause a communication to be transmitted to the removed tracking module.The communication may cause the tracking module to update its locationto “unassigned”, “storage”, or a new location as the case may be. In oneexample, the tracking module may include a user interface (e.g., seeFIG. 4C) allowing a user to view the device data elements associatedwith the tracking module. In the above or another example, thecommunication may cause the tracking module to output a notificationthat it is not to be used, not to be associated with that location, oris to be moved to another location. The notification may include audio,text display, lights, or other indicia that when perceived by a userprovides the desired notification. In one example, tracking modulesinclude a notification button that when pressed by a user causes outputnotifications associated with the tracking module. In some embodiments,tracking modules are not configured to store an indication of anassigned location.

In one embodiment, the device management system 40 is configured toenable a user to assign tracking modules to players. Assignment oftracking modules may be based on player groupings for a round, forexample. With reference to FIG. 5C, the device management system 40 maybe configured to generate a device assignment user interface 420 thatallows a user to perform device assignment operations. In variousembodiments, the device assignment user interface 420 and the devicemanagement overview 400 may be provided in a tab format allowing a userto simply select the desired tab to perform device management or deviceassignment operations from either interface. In one embodiment, thedevice assignment user interface 420 may receive groupings from thegroupings engine and automatically assign tracking modules from a devicelist to the groups and players.

The device assignment user interface 400 may include various deviceassignment elements. For example, the device assignment may includeelements selected from one or more of (a) device list 421, (b) devicesetup list 422, (c) save device setup 423, (d) menu 424, (e) event 425,(f) round 426, or (g) group presentation 427. The group presentation 427element may display the groups for device assignment along with playersassociated with the group, if available. For example, the grouppresentation 427 may include one or more of (a) group number 428, (b)player name 429, (c) device name 430, or (d) device status 431.

Device list 412 may include a list of devices not assigned to a groupnumber. Device setup list 423 may include a stored configuration ofdevice assignments to a group layout. In certain embodiments, a savedevice setup 423 operator may be provided as an option operable to savea device setup for a set of groups. Menu 424 may contain one or moreadditional options that are not visible for quick selection on the mainpanel. Event 425 may identify the event in a golf tournament or otherevent that the device assignments for each group will be reviewed andmanaged. Round 426 may identify the round of an event that deviceassignments will be reviewed and managed.

As introduced above, the device assignment elements may include a menu424 that contains additional options that assist a user in the setup fordevice assignments. In one example, the menu 424 may include a “locationselect” option enabling a user to select or specify a location for oneor more devices that will be used for device assignment. In the above oranother example, the menu may include a “tournament” option enabling auser to select the tournament. The tournament option or another optionmay be available to specify a tour in which the tournament isassociated. It will be appreciated that the assignment elements may beprovided in any suitable presentation format and elements referencedwith respect to the menu 424 may be provided on the main deviceassignment user interface 420 display.

In one embodiment, the device management system 40 may be configured toload a shell of group numbers and the devices assigned to that group. Invarious embodiments, each assignment in the group may be in sequentialorder. The order may be static unless assigned and re-assigned to thegroup. As introduced above, the device list may contain the list of alltracking modules that have not been assigned to a group and, hence,available for assignment. The device management system 40 may beconfigured to enable a user to assign devices in the device list to agroup. A user may further be enabled to assign the devices in a specificorder in the group. Upon assigning devices to a group, the user may savethe allocations via the save device setup operator.

The group presentation provided on the device assignment user interface420 may be configured to provide the group number and the devicesassociated with that group. If a selected round has players, the grouppresentation may show each of the players associated with the group inteeing order. For example, when a round is selected from the round 246element, the players for the groupings may be automatically filled inthe group presentation. Group number 428 may include a number associatedwith the groupings for the round and that may also be assigned to eachtracking module assigned to the group for deployment. Player name 429may include the name of each player that is assigned to the group, andmay be presented in teeing order. Device name 430 may include the nameof the device. Device status 431 may include details of the device'scurrent hardware functions such as battery life and signal strength.

In one embodiment, assigning tracking modules to a player associates atracking module identification number with a player at the backend ofthe STTM system such that data obtained from and/or recorded by thetracking module is accompanied by the identification number and the STTMsystem components receiving the data, e.g., companion device, locationsystem, validation system, data management system, device managementsystem 40, and/or data platform, associate the identification numberwith the assigned player. Such STTM system components may receive theplayer and tracking module identification number assignments set by thedevice management system 40 for such purposes. In one example, thecompanion device receives the player and tracking module identificationnumber assignments set by the device management system 40 and associatesthe tracking module data with the player when scoring, e.g., storingand/or transmitting to the same STTM system components. As introducedabove, the STTM system may include a location network configured fordevice-side and/or network-side location tracking, e.g., utilizing anUWB anchor network. On a network-side location tracking use case, thedevice and player assignments may be transmitted to system componentsconfigured to calculate locations from data collected by thenetwork-side location network or subsequently used to associatecalculated location data of a tracking module with that of the assignedplayer.

As introduced above, and with reference to FIGS. 6A-6G, the STTM systemmay include a round management system 60 configured to manage rounds andgroupings for players that are playing in an event. The round managementsystem may provide data managers data access to round managementoperations locally, remotely, and/or from any location via managementdevices. In various embodiments, groupings may be managed by a groupingsengine 500 configured to one or more of store tee times, adjustment toprior published tee times, or record the order of players in each teetime group. In some embodiments, the groupings engine 500 may beconfigured to automatically generate groupings for future rounds basedon scoring rules. Rounds may be managed by a rounds engine 501configured to manage one or both of round states or round cuts.

The groupings engine 500 may be configured to manage groupings.Management of groupings may include creating groupings of players. Inone example, the groupings engine 500 may be configured to enable a userto define and manipulate groupings for any round of any event. FIG. 6Aillustrates a user interface of the groupings 500 engine comprising agroupings management panel 503 configured to interface a user withvarious operations of the groupings engine 500. In various embodiments,the groupings management panel 503 may be configured to provide one ormore elements, e.g., interface elements, display elements, or associatedoperational elements, selected from (a) groupings presentation element504 comprising a list of groups with their associated tee times for eachsegment; (b) a view by segment element 505 operable to enable the userto view each segment, a defined portion of the segments, or all segmentsat once; (c) a player list element 506 that identifies players that havenot been grouped or that are otherwise available to be grouped; (d) asegment list element 507 that identifies segments that have been createdfor a particular round; (e) a round selection element 508 operable toenable a user to select a round for reviewing and editing of groupingswherein segments are associated with the round; (f) a segment profileselection element 509 operable to load a previous created profile withsegment information; (g) an edit segments element 510 for creating orchange segments for the round; (h) a generate groupings element 511configured to generate groupings based on predefined and/or definablesegment rules for the round; (i) a remove players element 512 configuredto remove players in the grouping presentation component while retainingthe tee time data; (j) a generate shell element 513 configured togenerate groupings without players but with groupings based on segmentrules for the round; (k) a clear groupings element 514 conjured toremove players and tee time data from the groupings presentationcomponent; (l) a groupings states element 515 comprising a selectablelist of grouping states; (m) a revision element 516 to access operationsof a revision editor operable to adjust groupings and flag a round asgroupings revised; or (n) a player status element 517 providing accessto operations of a player status editor operable to change a player'sstatus for a round in an event.

With further reference to FIG. 6B, the groupings engine 500 may beconfigured to display a groupings presentation 518. The groupingspresentation 518 may be displayed in whole or in part or be accessiblevia interaction with the groupings presentation element 504 (FIG. 6A).In the illustrated embodiment, the groupings presentation 518 includesgrouping data elements provided in rows wherein each row represents agroup of players with tee times. For each group, one or more of thefollowing grouping data elements may be provided: (a) segment number 519providing the segment number associated with the group, (b) group number520 associated with the group of players for a specific tee time, (c)tee time 521 presenting the current time created for the group, (d) teetime data 522 presenting the date of the tee time created for the group,(e) course 523 presenting the course the group will be playing for theidentified tee time, and (f) player 524 providing the name of the playerassigned to each group, which may be presented in order of play.

As discussed in more detail below, various grouping and/or round datamay be subject to revision. In the illustrated display, grouping datathat has been subject to revision from an original value are displayedwith a label, which is an (R) in this example, to denote revisions tothe original tee time.

In various embodiments, the groupings engine 500 may provide variousviewing and/or editing options with respect to groupings and relateddata elements in the groupings presentation. For example, the groupingsengine 500 may provide an interface element allowing a user to sortcolumns of the data, e.g., by numerical value, alphabetically,chronologically, or other suitable data point characteristic. In oneexample, an interface element may be provided such that a user mayselectively cause the groupings engine 500 to present groupings bysegment number or all segments at once. In the above or another example,the groupings engine may be configured to enable a user to edit datapoints in the rows of the data. For instance, editing features may beprovided together or separately from the displayed data. In oneembodiment, the displayed data elements referenced in FIG. 6B maycomprise interface elements that display respective data point valuesand are configured for user interaction to optionally edit the datapoint value. The groupings engine 500 may provide editing features withrespect to the grouping data elements selected from (a) a segment numbereditor that includes a list of available segments that have been createdor loaded from a profile; (b) a group number editor operable to enable auser to change a group number value, typically a positive integer; (c) atee time editor operable to enable a user to change a tee time (e.g.,hour:minute); (d) a tee time date editor operable to enable a user tochange a tee time date (e.g., month:day:year); (e) a course editoroperable to enable a user to change a course, which may include aselectable list of courses available for the tournament and eventselected; (f) a player editor operable to enable a user to change aplayer (e.g., selecting a player may provide a field to enter anotherplayer or may display a list of selectable players, which may includedrag and drop or other selectable methodology), or (g) combinationthereof. As noted above, the displayed elements in the groupingpresentation 518 may comprise interface elements. In one embodiment,interaction with such interface elements may cause the above editoroperations. In one configuration, the groupings engine 500 is operableto enable a user to selectively add rows, delete rows, or both.

With further reference again to FIG. 6A, the player list element 506 maydisplay or be configured to selectively display a list of all players ina field for the selected event who have not been placed in the groupingspresentation 518 or been assigned to a group. In various embodiments, auser may assign a player to a tee time via interaction with the playerlist element 506 or via another interface element in the groupingspresentation 518. In one embodiment, the player list element 506 isconfigured to display a player name and a player's event score total,which may be relative to par.

The grouping engine 500 may utilize segments and segment profiles. Asegment may include a block of tee times that present a starting phasefor a round. For example, two segments of groups may include onestarting on hole one and the other starting on hole ten. A segmentprofile may include a set of segment rules that the groupings engine 500uses to assist in groupings creation. The groupings engine 500 mayinclude or access one or more segment profiles. Segment profiles may beloaded and/or created using a segment data manager. In variousembodiments, the groupings engine 500 may be configured to automaticallyapply one or more segment profiles to a round. For example, a user mayone or more of define, save, load, or delete profiles that the groupingengine 500 applies to an event or round thereof. In one embodiment, thegroupings engine 500 is configured to allow a current user to searchsegment profiles and/or users profiles or another user that includesassociated segment profiles, such as segment profiles created by orpreviously used by the other user. In one example, the user may selectsegment profiles and import the selected profiles into the current eventor their profile or export segment profiles to the profile of the otheruser.

FIG. 6C illustrates a segment profile management interface 525 thatincludes example elements of a segment profile along with definitions ofoptions to edit the data elements or create a new segment. The exampleelements and definitions of options to edit may be available to asegment data manager to create a new segment profile. The elements mayinclude one or more data elements selected from (a) segment numberselection 526 including a list of the segments that have been createdfor a selected round; (b) segment priority 527 comprising a positiveinteger value that cannot be duplicated is set in another segmentassociated to the round such that a particular segment may exist in thesystem once per round; (c) course 528 including a list of courses thatare associated with a selected event; (d) date 529 identifying a datewhen the tee times are to start the play; (e) tee time 530 identifyingthe initial tee time for starting or ending; (f) tee time(starting/ending) 531 comprising an option to flag the tee time as thestarting tee time or the ending tee time; (g) time interval 532 used tospecify a time interval between times from the start or end time set inthe tee time (above) and the tee time (starting/ending) (above); (h)groups at interval 533 that, if set, identifies the number of groupsthat will be at one interval while the remaining groups are at adifferent interval as applied using the first interval (below) andremaining interval (below); (i) first interval 534 representing thenumber of groups as defined in the groups at interval (above); (j)remaining interval 535 representing the time interval for the groups notdefined in the groups at interval (above); (k) best score last/first 536that identifies if the player with the best score is set in the firsttee time or the last tee time; (l) starting hole 537 for all tee timesfor the segment; (m) players per group 538 identifying a maximum numberof players that are assigned to a group; (n) number of groups 539identify the initial number of groups for the segment, or (o)combination thereof. A segment list panel 540 may comprise a display ofall the data elements for each segment for the segment profile that isloaded in the segment profile management interface 525.

In one configuration, the groupings engine 500 is configured to enable auser to create or delete a segment. For example, the elements of asegment profile may be editable via interaction with the elements in adisplay wherein the options to edit the elements comprise interfaceelements a user may use to edit data elements of the segment profile orotherwise. For example, to delete a segment a user may select to deletea segment 541 from the segment profile manager interface 525. To createa new segment a user may select create a new segment 542 from thesegment profile manager interface 525. Upon selection, the user may bepresented with default data elements with the next sequential numberfrom the current segments in the profile, the next sequential numberfrom the current segments in the profile, the current selected course,or predefined time interval. In various embodiments, additional dataelements may be set to other default values or left blank to be furtherspecified by the user.

When loading a pre-existing segment profile, the number of groups persegment may be defaulted to the size of the field for the round dividedby the number of segments. When editing a segment after the number ofplayers has been updated, the number of groups in each segment may beupdated based on the size of the field for the round divided by thetotal number of segments. In one configuration, if there is an unevennumber of groups in a multi-segment profile, the odd group may beautomatically placed in the highest even segment priority by default.

After editing or creating a new segment profile, a user may save thesegment profile 543. In one example, the user may be prompted to providethe profile with a name, which may be a new name for the profile. Theuser may also save the profile and override the current segment profilewith the updated profile.

With reference again to FIG. 6A, the groupings engine 500 may beconfigured to generate groupings. In one embodiment, a user may interactwith the generate groupings element 511 to generate groupings for anevent, round, or segment thereof. For example, when the generategroupings element 511 option is activated the groupings engine 500 mayutilize the current segment profile to create groupings. Tee times maybe generated based on the configuration of each segment in the segmentprofile, described above.

When generating groupings, a player slot may be identified for eachplayer based on the number of players per group, as defined in thesegment configuration, with the slot representing the order each playerwill play. The slot referenced as one being the first player to play,the slot referenced as two being the second, and so on. If multiplesegments are part of the segment profile for the round, the groupingsengine 500 may automatically initiate player assignments starting withsegment set as priority one and work in sequential order as each segmentis completed with player assignments. If best score last/first 536 isset to last, player assignments may begin at the last tee time of thesegment and operate backwards from there. If best score last/first 536is set to first, player assignments may begin at the first tee time ofthe segment and operate forwards from there. With respect to playerselection and slotting when best score last/first 536 is set, thegroupings engine 500 may assign the player with the best tournamentscore in the first slot, the player with the second best score in thesecond slot, and so on until a player has been assignment to each slotin a tee time before moving to the next tee time. In some embodiments, asegment profile may tie multiple players. In one example, if multipleplayers are tied, the groupings engine 500 may apply the following orderrules to determine the next player for assignment, such as: (a) earliesttee time from previous round; (b) highest segment priority from theprevious round, with the highest being first; (c) the lowest slotnumber, with the lowest being first; and (d) the course with the highestpriority, with the highest being first.

The groupings engine 500 may be configured to utilize the elements of asegment profile for a selected round to create a groupings shell or forgroupings automation. For example, when the generate groupings element511 is activated, the groupings engine 500 may be configured to createthe groupings using the profile that is currently selected for theround. The tee times may be generated based on the configuration of eachsegment in the segment profile, as described above. When the generateshell component is activated the groupings engine may be configured topresent a slot based on the number of players assigned to each group foreach segment to generate a grouping's shell.

Each round may be associated with a grouping state. The grouping statemay be editable via the grouping state element 515. In one embodiment,grouping states may be selected from one or more of (a) draft, (b) to bereviewed, (c) reviewed, (d) official, or (e) combination thereof. A“draft” state may be utilized while a user is working on creating thegroupings that are needed for the round. In one embodiment, the “draft”state may be set as a default state when first creating the groupings. A“to be reviewed” state may be set when a defined set of groupings isready for review. A “reviewed” state may be set when the defined set ofgroupings has been reviewed and has been determined by the review to beready to transition to an “official” state. An “official” state may beset when the set of groupings have been reviewed and approved, ready fordistribution.

In various embodiments, the groupings engine 500 may be configured toapply one or more groupings state rules. For example, the groupingsengine 500 may restrict setting of groupings states that progress towardofficial that skip a groupings state. In one example, a “reviewedgroupings” state cannot be set until a groupings state of “to bereviewed” has been set and the “official” groupings state cannot be setuntil the groupings state of “reviewed” has been set. In variousembodiments, the groupings engine 500 is configured to log all groupingsstates with a time stamp of selection by the user. The user making thegroupings state selection may also be logged and associated with theselection.

In some embodiments, draft groupings are stored for subsequent review bythe groupings engine 500. In one example, the stored draft groupings arenot distributed to other STTM system components. In some embodiments,review may be performed to modify groups, e.g., to create featuredgroups of interest, ensure a player is not in early groups multipleweeks in a row, separate players known to play slow, separate playersthat do not get alone, etc. In one example, when groupings data enters astate for review, management users may review the data and thereafterset the groupings date to an “approved” state once signed off. Once thegroupings data has been approved and the associated state set to“approved”, the groupings data may be available to other STTM systems.

As introduced above, the groupings engine 500 may include a revisioneditor. In the illustrated embodiment, the operations of the revisioneditor may be activated by interaction with the revision element 516 inthe grouping management panel 503. Revision state may be specified invarious states. For example, revision states may include a “to berevised”, “revision”, and “revised state”. A “revised” state may be setas a default state that is set prior to any revisions being made aftergroupings are official and before a revisions process starts. A“revision” state may be displayed when a user utilizing the revisioneditor is in the process of revising groupings that already have a stateset to “official”. A “revised” state may be displayed when the groupingsreview process is completed and it is a change from the originalgroupings that were set as the official groupings state. In oneembodiment, when a change is made to the groupings or data elementsupdated by the revision editor, the revision state may automatically beset to “revision” and the groupings state restarts at the “to bereviewed” state. In a further or another embodiment, the “revised” statemay be set when the groupings validation process is completed any timeafter the original groupings were set to an “Official” groupings state.

The revision editor may be equipped with various operations that a usermay use to adjust tee times from a current groupings tee times. Forexample, FIG. 6D illustrates an interface of a revision editor 545configured to adjust tee times using a revise based on offset element546 or a revise using base time element 547 methodology. The revisebased on offset element 546 may cause the revision editor 545 to apply arevise based on offset methodology that utilizes a start and end group.The start and end group may be predefined or set by a user, e.g., byinteracting with the start and end group element 548, and represent thestarting group and the ending group that the tee times will be adjusted.The revise based on time element 547 may cause the revision editor 545to apply a revise based on offset methodology, which in one embodimentmay also include an adjustment of time that may be specified viainteraction with an adjusted time (+/−) element 549 in the illustratedinterface, comprising an amount of time that will be applied to anoriginal tee times of the groups identified by the setting of the startand end group step. The start and end group and/or adjusted time (+/−)elements 548, 549 may include interface elements including fields forentering text, selectable lists of groups and/or time differences, orother suitable interface elements. The revise using base timemethodology may allow a user to utilize a new base tee time, viainteraction with a new base time element 550, that replaces the originalbase tee time and the adjustments for the remaining tee time arethereafter generated based on data elements defined in the segmentprofile for the round. In various embodiments, when a revision is usedand applied, the round state is set to “revision” and the groupingengine 500 begins a grouping validation process.

As introduced above, the player list element 506 may contain or provideaccess to a list of all players in the field for the event. In someembodiments, a player status for the event and/or round may beassociated, e.g., displayed, with the name of the player. In someembodiments, the groupings engine 500 may include a player status editorconfigured to change a player status. For example, in one configuration,a user may highlight a player in the player list and select the playerstatus component to access the player status editor to change the playerstatus for the selected player. With reference to FIG. 6E, depicting anexample interface of the player status editor 560, a list of statusoptions 561 may be provided that a user may use to set a player statusfor a selected player. A set status operator 562 may be provided toenable a user to set a status for a selected player. Various playerstatus options may be provided, which may include one or more of (a)uncut—status that identifies players who are still eligible to play inthe event; (b) cut—status that identifies players who are flagged cut,which may be manually set or automatically updated after a cut rule hasbeen run, as described in more detail below; (c) withdrawn—status thatidentifies players that has withdrawn from a round; (d)disqualified—status that identifies players that have been disqualifiedfrom a round; or (e) made cut but did not finish—status that identifiesplayers that are to be paid official money but do not continue to playin the remaining rounds. In various embodiments, the player list 563 mayautomatically update upon setting a player status. The player statuseditor 560 may be configured to provide additional options to furtherdefine a player's status. For example, the player status editor 560 mayprovide a user an option to define if a player status entered by theuser as “withdrawn” will also be set for future rounds for the player.When the status of a player is set to “withdrawn”, “disqualified”,“cut”, or “made cut but did not finish”, the player may be removed fromthe groupings presentation 504 and the player list 506 in the groupingsmanagement panel 503 for the rounds identified.

As introduced above, the round management system may include a roundsengine configured to enable a user to define round states different thanthe round states as defined relative to the various grouping creationprocesses described above with respect to FIGS. 6A-6E. In someembodiments, the rounds engine is also operable to enable a user tocreate and run player cuts on a round. In one example, the rounds enginemay be configured to provide playoff management operations along withround states and/or cuts.

FIG. 6F illustrates a user interface of the rounds engine 501 comprisinga rounds management panel 570 configured to interface a user to variousoperations of the rounds engine 501. In various embodiments, the roundsmanagement panel 570 may be configured to provide one or more elements,e.g., interface elements, display elements, or associated operationalelements. In the illustrated embodiment, the elements include one ormore round selection elements selected from (a) round selection element571, (b) round states element 572, (c) a suspend type element 573, and(d) suspend round element 574.

The round selection element 571 may be operable to select a round forcontrol. The round selection element 571 may comprise or cause aselectable listing of rounds available for an event to be presented foruser selection.

The round states element 572 may be operable to select a round state,and may comprise or cause a selectable listing of available round statesto be presented for user selection. In some embodiments, one or moreround states may be automatically set by the rounds engine 501. Invarious embodiments, round states may include (a) not started—defaultstate prior to groupings being set to official; (b) groupingsofficial—state corresponding to and available only when the respectivegroupings of the round have been set as “official”, as described above;(c) in progress—state that is automatically set when the first stroke orscore of a round is created, which may additionally or alternatively beset manually in some embodiments; (d) suspended—state that is set if theround is interrupted due to weather or other circumstances; (e) playcomplete—state that the round may automatically be set to when the lastscore for a round is created, which in some embodiments may additionallyor alternatively be set manually; (f) official—state that is set when nomore changes to the round data will be needed such as stroke informationor score changes; (g) cancelled—state set if the round has beencancelled and will not be played for the remaining time of the event; or(h) or combination thereof.

In various embodiments, when a round state is set to “suspended” theuser may use the suspension type element 573 to select a suspensiontype. In one example, the round engine 501 may require or prompt a userto select a suspension type when setting a round state to “suspended”.In various embodiments, the suspension type element 573 may include orbe operable to cause a selectable listing of suspension types to bepresented for user selection. Example suspension types may include oneor more of delayed, cancelled, suspended, or done for the day.

In various embodiments, when a round state is set to “suspended” theuser may use the suspension reason element 574 to select a suspensionreason. In one example, the round engine 501 may require or prompt auser to select a suspension reason when setting a round state to“suspended”. In various embodiments, the suspension reason element 574may include or be operable to cause a selectable listing of suspensionreasons to be presented for user selection. Example suspension reasonsmay include weather or environmental reasons. In one configuration,suspension reasons may include one or more of darkness, rain, lightning,fog, wind, or frost. In a further configuration, suspension reasons mayinclude a text field for entry of a custom reason for suspension, e.g.,tornado warning, equipment issues, or course maintenance.

The round management panel 570 may also include one or more elementsconfigured to interface a user with operations of the round engine 501with respect to cut management for a round. It will be appreciated thatwhile certain elements are depicted in a single or same panel, suchelements may be provided in many different ways, including differentpanels and/or in different combinations. With respect to cut managementelements, two selectable listings are available in the illustratedembodiment: an uncut player list element 575 and a cut player listelement 576. The uncut player list element 575 includes or is operableto cause a selectable list to be presented of all players for the roundthat have not been flagged as cut. The cut player list element 576includes or is operable to cause a selectable list to be presented ofall players who have been cut for the round. The cut management elementsalso include a run cut element 577 and an uncut all element 578. The runcut element 578 is configured to run the cut rules based on the selectedsettings discussed below and set the defined players of a player statusof cut. The uncut all component 578 is configured to remove the playerstatus of cut.

With respect to the cut rules, the selectable settings may includenumber to make cut 579, number to make cut and play 580, max strokesfrom lead 581, target cut 582, include amateurs 583, or combinationthereof. Number to make cut 579 may correspond to a number of playersthat will make the cut based on scores and have player status remainuncut, while all other players who are set as uncut will be set to aplayer status of “cut”. Number to make cut and play 580 may correspondto the number of players that will make the cut based on scores and willcontinue to play proceeding rounds. If this is set then the differencebetween number to make cut 579 set above and number to make cut and play580 may include players whose player status will be set to “made cut butdid not finish”. All other players may be set to a player status of“cut”. Max strokes from lead 581 may correspond to a number of playerswho make the cut being a number of par relative strokes from the lead.Target cut 582 may correspond to a number of players who make the cutthat is closest to the value set, whether above or below the value. Ifthe value of players is the same above and below, all players above thevalue may be considered “uncut” while all remaining players will havethe player status of “cut”. Include amateurs 583 may correspond towhether amateurs are to be included as part of the cut rules. If set,then a competing amateur is part of the cut rules. If not set, then thecut rule will not include the amateur. Include Amateurs 583 may beselected in addition to the other cut rule components. It will beappreciated that different and/or additional settings may be provided ifselectable settings are included.

The round management panel 570 may also include a save round infoelement 585 giving a user an option to save or cancel changes made tothe round states and/or the cut configuration. In one embodiment, when acut rule definition is saved for a round, the cut rules may be used forlive projected cut presentations in the STTM system. However, the roundengine 501 may be configured to not set the player status as definedabove until the user runs the cut rule option.

The round management panel 570 may also include one or more elementsconfigured to interface a user with operations of the round engine 501with respect to a playoff round creator. For example, the roundmanagement panel 570 includes a playoff creator component operable toprovide access to the playoff round creator configured to create aplayoff for a selected round. FIG. 6G illustrates an example userinterface of the rounds engine 501 configured to interface a user withvarious operations of the playoff round creator 586.

The playoff round creator 586 may include various elements for defininga playoff round. For example, the playoff round creator 586 may includeone or more definable elements selected from (a) playoff type 587, (b)playoff number 588, (c) position decided 589, (d) starting hole sequence590, (e) repeating hole pattern 591, (f) player list 592, (g) saveplayoff 593, (h) start playoff 594, or (h) set winner 595.

The playoff creator 586 may be configured to include a plurality ofselectable playoff types for selection via the playoff type element 587,such as one or more playoff types selected from “sudden death”, “numberof holes”, and “number of holes/sudden death”. “Sudden death”corresponds to a playoff format wherein, starting on a first playoffhole, players in the playoff play until a player has a better strokescore than the other players in the playoff. If more than two playersare playing, the players having higher scores than the best score on thehole are eliminated. “Number of holes” corresponds to a playoff formatwherein the playoff beings with all players in the playoff playing anumber of holes, as defined in the starting hole sequence below. If aplayer has the best score, then that player wins and the playoff isover. If there is a tie after the defined number of holes, the playoffrepeats the defined number of holes. This process continues until aplayer has a better score than the other players in the playoff.Multiple players in this playoff type can be eliminated if their scoreis not better than the best score. “Number of holes/sudden death”corresponds to a playoff format wherein the playoff beings with allplayers in the playoff playing a number of holes, as defined in thestarting hole sequence below. If a player has the best score, then thatplayer wins and the playoff is over. If there is a tie after the definedholes, then the playoff goes into sudden death as defined above.

The playoff number element 588 may set or be operable to set the numberplayoffs enabling a user to store multiple playoffs for a round. Thepositions decided element 589 be define or be operable to define whatplayer positions will be played for in the playoff. For example, playoffpositions decided may include position one for multiple players tied forfirst or position three for multiple players tied for third.

The starting hole sequence element 590 may define or be operable todefine the holes that the playoff will be played first. For the “numberof holes” playoff format, the starting hole sequence element 590provides the defined holes for the format. The repeating hole patternelement 591 may define or be operable to define the repeating holepattern for a “sudden death” playoff format in an instance where awinner has not been identified after the starting hole sequence holesare completed.

The save playoff element 593 may be operable to save the playoffsettings. In some embodiments, the playoff settings may be saved withoutstarting the playoff.

The start playoff element 594 may be operable to start the playoff. Inone embodiment, the playoff may not be started in the round generatoruntil play is completed in the selected round. In one example, theplayoff may require validation that the previous round has completed. Inanother embodiment, the playoff may start before the previous round hasbeen completed.

When play is completed in the selected round a player list 592 isimported into the playoff round creator 586 by analysis of scoresaccording to the playoff number 588 and/or position decided 589 valuesset. The playoff round creator 586 may then be configured to apply theremaining playoff settings to create a new round according to the rules.The players qualified for the playoff round may be placed in groupings,which may include automatically, as described above, with a max fourplayers per group; however, in some embodiments, manual group placementmay be used. In some embodiments, the groupings for the playoff may beconfigured to be reviewable via the groupings presentation. In anotheror a further embodiment, the round state may automatically be set to“groupings official”.

As introduced above, companion devices may be used by scorers to performscoring functions. Scorers may include caddies, players, or others thatare viewing play. Companion devices may execute or run an STapplication. Companion devices may be equipped with wireless datacommunication transceivers configured to wirelessly transmit score data,which may include event data, to STTM system components. During play,each group may have an assigned companion device that the scorer uses tocollect score data. The score data may be transmitted to the managementsystem, which may be configured to handle data received from a pluralityof companion devices during play. The companion devices may beconfigured with various wireless communication technologies as describedabove, which may include short range and/or long range communicationswith the devices of the STTM system. Companion devices may be configuredto communicate with tracking modules to trigger and/or define datacollection events that may be used to officially score player rounds.For example, companion devices may be carried by scorers accompanyinggroups of players or otherwise observing play. In various embodiments,companion devices may not be configured to communicate with trackingmodules and companion devices may transmit location and/or location datato the location system, location elements, and/or other STTM systemcomponents. Companion devices may similarly transmit collected scoredata and/or event data to the location system, location elements, and/orother STTM system components.

In various embodiments, the companion device may be configured towake-up the tracking module, initiate an event capture such ascollection of event data, e.g., event capture, location/positiondetermination or related data for processing and determination of thesame by the companion device or another processing device. In oneembodiment, the tracking module may be configured to receiveinstructions for event capture. The instructions may be transmitted by acompanion device or management device. For example, a companion deviceand/or management device may be networked with or otherwise operable toprovide instructions and/or receive instructions or data from multipletracking modules. It is to be appreciated that management devices mayinclude or provide data to the location system.

The scorer, utilizing the companion device, will typically accompanyplayers whose score the scorer is tracking; however, in someembodiments, the scorer may remotely view the player via a live ordelayed feed. When the scorer is also entering events setting timestamps for address or when a ball is hit, that may be paired with thelocation of the tracking module to provide a proxy for ball locationfollowing the previous shot or ball starting location for a currentshot, the feed should be live or with a precisely known delay as toretain accuracy linking the location of the player relative to thelocation of the ball. In a remote viewing use case, the tracking modulemay be configured for communication with a management device orintermediate relay device via a suitable communication protocol, whichmay include short range communication protocols or long rangecommunication protocols depending on the proximity of the managementdevice or intermediate relay device, in order to provide its locationdata or calculation parameters. In configurations wherein location ofthe tracking module is subject to network-side calculation by anotherdevice, the other device may be in direct or indirect communication withthe management device.

The ST application or companion device running and/or accessing the STapplication—which may be local, remote, web-based, or cloud-based—may beutilized by a scorer to score one or more rounds of golf, typically agolf tournament event. The collected scoring data may be stored ortransmitted by the companion device as discussed in more detailelsewhere herein. Reference to transmission of scoring data, which mayinclude event data and/or location data, from the companion deviceand/or tracking module may include indirect or direct transmission toone or more the location system, management systems, and/or dataplatforms. For example, scoring data may be immediately or subsequentlytransmitted to the location system and/or one or more management systemsfor further data management, data review, data correction, scorevalidation, data analysis, data storage, location identification,location calculation, zone identification, or applications configured toperform other STTM system operations. Data viewing platforms may referto distribution to subscription services or platforms, such as those ofdownstream clients, business or consumer level platforms, private orpublic networks for fan consumption alone or together with other data,surface web platforms, or the like. In various embodiments, the scoringdata may be distributed or made available for use or integration with aweb-app, mobile app, or other application for public or private viewing,analysis, or archival storage.

The ST application may be configured for multiple selectable scoringlevel operations. For example, in a stroke level operation, the scorermay utilize the ST application to record strokes as they occur, withoututilizing the location functions of the tracking module or utilizationand/or incorporation of the tracking module as described herein.

When utilizing the tracking module to obtain location information, theST application or other STTM system application or service may combinelocation data with stroke level data. In laser operator level scoring,the scorer may utilize the ST application to record strokes withoutadditional location information or may also track player location viathe tracking module for use in combination with laser location tracking,either via a manual laser pointing device such as those used by PGA Tourlaser operators or via operation of an automated laser system thattracks or continuously tracks ball location throughout a round. Thelaser information may be output or translated into a coordinate gridsystem based on a survey or GPS or similar mapping of the course. In acombination use configuration, the location data obtained from thedifferent techniques may be utilized for separate end uses, combined foranalysis to achieve greater accuracy, or one location technique may beused as a backup or reference for another. In one embodiment, thecompanion device and ST application may be configured to allow a singlescorer to collect stroke level data for all players in a single group.

In one embodiment, the companion device may be pre-loaded with orconfigured to access, via the ST application, specific event data suchas one or more of (a) par values for a particular course, (b) coursehole sequence (which may be associated with par values), (c) pre-definedfrom locations (which may include location indicators as well as fromlocations available for selection in a “from location” screen), (d)score level of event (which may be recordation of stroke only orutilization and/or incorporation of location tracking, e.g., GPS, UWB,BLE, Wi-Fi, cellular, or the like, range finder, laser operator, orcombination thereof), (e) course name, (f) player group data for anassigned group, multiple groups, or all groups of players of an eventsuch as player names in a group, player number in a group, player image,e.g., headshot, or (g) combination thereof. In one example, the STapplication is executed, at least in part, e.g., in a cloud-basedenvironment, and the above event data is automatically provided to thecompanion device, such as upon startup. If the event is conducted onmultiple courses, course data for a particular or multiple courses maybe provided or selectable by a scorer, e.g., via a user interface.Course name and number may be provided. The companion device mayautomatically be provided with round details, which may include groupupdates, group assignments, event changes, event notices, or other rounddetails.

In one embodiment, using the ST application, the companion device may beconfigured to receive group location data. A scorer may interface with auser interface of the companion device to input group location data byany suitable method, such as input into a provided field, select from alist of displayed options, or the like. In one example, when the playersin a group are on the tee box, the scorer inputs or selects “tee”. In afurther or another example, when the first caddie or player of the grouparrives at the player's ball in the fairway, the scorer may input orselect “fairway”. In a further or another example, when the first caddieor player of the group arrives at player's ball around the green, thescorer may input or select “green”.

The outputs of the data management system, device management system,rounds management system, groupings engine, and/or rounds engine may betransmitted to the ST application to conform the operation of the STapplication to the outputs. For example, groupings output may be sent tothe ST application to populate one or more groups to which a companiondevice is assigned.

As introduced above with respect to FIG. 3 , in various embodimentsgroup and/or player location may be tracked automatically via locationtracking techniques and associated location networks, e.g., GPS, Wi-Fi,RFID, BLE, UWB, NFC, cellular, or the like. For example, the STapplication may incorporate geo-fencing that triggers group locationchange at pre-defined boundaries. Geo-fencing may also be applied byother STTM system applications by tracking the location of the companiondevice and/or tracking module.

To track player hits, the companion device may present a selectable listof players from which the scorer may select. When tracking player hits,the companion device may be configured to present a selectable list oflocations the player will be hitting the shot from. Example locationsmay include tee, fairway, green primary rough, bunker, sand, fringe,waste area, or native or natural area. In one configuration, “fromlocation” is to be set at any time for a player and have it be “sticky”for the next shot. In other words, the scorer may set a player's “fromlocation” as soon as that location is known and have that value persistuntil the scorer either changes the location or indicates the ball hasbeen hit.

In one example, the scorer may also input when the player is addressingthe ball. This may be entered as an event, e.g., upon the occurrence of,when the player first addresses the ball, or as a toggle. In a togglecase, the user interface of the companion device may include an“address” button that the scorer presses when the player is addressingthe ball. The scorer may subsequently press a “shot hit” button orotherwise indicate that the ball has been hit. The “address” may beinterpreted by the ST application as remaining down until the scorerpresses or taps the “shot hit” button or other indicator at which timeboth addressing and hit events are sent or recorded. In anotherconfiguration, the scorer maintains contact with the “address” buttonuntil the ball is hit. When the scorer releases the “address” button,the release is interpreted as the ball being hit. In some embodiments,interaction with the address button is transmitted in real time beforeindication of the ball being hit. In other embodiments, the interactionsmay be transmitted together in real time following the shot being hit ormay be stored locally for subsequent transmission. When collectinglocation data, such as location coordinate data, for shots utilizing thetracking module, the ST application may be configured to map thetracking module assigned to the player to the player's name. When thescorer indicates the ball is hit, the location of the tracking module iscaptured as described elsewhere herein and recorded. In someconfigurations, capturing the location of the tracking module may betriggered via interaction with an “address” button.

The companion device may also be configured to score various stroketypes, such as drop, penalty, and provisional. For instance, thecompanion device may query the scorer or request entry of a shot type,if applicable. If the scorer selects “drop”, the companion device mayprompt the scorer to indicate if there was a penalty. If the scorerselects “penalty”, the companion device may prompt the scorer toindicate if there was a drop. If the scorer selects “provisional”, thecompanion device, one the next stroke, may prompt the scorer to indicateif the provisional is being used. If yes, and the shot location was“from the tee”, a penalty stroke may automatically be added to theplayer's score. If not, and the shot location was “from the tee”, thecompanion device may prompt the scorer to indicate if there was a dropand, if so, automatically add a penalty stroke to the player's score.

As introduced above, the user interface may present a “shot hit” buttonor other indicator that the scorer may interact with to indicate theball has been hit. In one example, the “shot hit” indicator is a buttonthat a scorer taps when the ball is hit. In another example, the “shothit” indicator is a button the scorer presses and holds until the ballis hit wherein release of the button indicates when the ball is hitrather than “pressing”. In a further example, multi-stage “shot hit”indicator or multiple indicators may be used to indicate at least two ofaddress, location time stamp, and shot hit. For example, a two-stage“shot-hit” indicator may be used to indicate address and/or location ina first stage and location and/or shot hit in a second stage. In oneconfiguration, the scorer may press a two-stage indicator button whenthe player is in the address position and release the indicator buttonwhen the ball is hit, wherein pressing sets the location time stamp andrelease is interpreted as the ball being hit.

In some embodiments, after the scorer indicates the ball has been hit,the scorer may be prompted to indicate if the ball is in the hole. Theinterface may present a button, swipe bar or field, or the like that theuser may interact with to indicate if the ball is in the hole. In oneexample, the scorer is presented with a bi-directional swipe fieldwhereby the scorer indicates “yes” or “no” by swiping the field in thedirection of the desired indication. In one embodiment, an “in the hole”prompt may be displayed if the scorer fails to interact with theassociated indicator within a predetermined number of seconds toindicate the ball is “in the hole”, the ST application may take the lackof indication as a null response having the value that ball is not inthe hole. In another configuration, the ST application may similarly beconfigured to take lack of indication as the ball being in the hole. Thescorer may have the option of indicating null response or allowing thetime to expire. For example, the scorer may swipe right for in the hole,left for not in the hole, or allow time to expire for not in the hole.After indicating the ball has been hit or that the ball is not in thehole, the user interface may automatically return to a group page fromwhich the scorer may select the same or next player taking a shot torecord the same. When the scorer indicates that all players are in thehole, the scorer may be prompted to indicate or have available a buttonor other indicator to proceed to the next hole. In another example, whenthe scorer indicates that all players are in the hole, the STapplication may automatically proceed to the next hole.

As noted above, the scoring data may be collected in real time andstored locally or transmitted immediately, upon the occurrence of anevent, such as collection of another piece of scoring data or when oneor all players finish a hole or group of holes, periodically, atscheduled intervals, when the companion device is in proximity of amanagement device (which may include a network access point or node),upon collecting a predetermined amount of data, or based on remainingavailable data storage.

With reference to FIGS. 7A-7V illustrating various user interfaces of anST application 700 according to various embodiments, a scorer mayinterface with the companion device to provide player descriptions. Theinterface may include various data input screens into which scorers mayinput data. The screens may include pre-defined selectable options,e.g., presented in listboxes, checkboxes, dropdown, input steppers, textentry fields, and the like. The ST application 700 may be pre-programmedto present one or more descriptive categories, each including aplurality of descriptive choices the scorer may select with respect to aselected or identified player. In some embodiments, the ST application700 may include a field into which a scorer may enter text descriptions.The descriptions may be entered into one or more predefine descriptivecategories selected by the scorer. In some configurations, the scorermay enter descriptive information or define a descriptive category byvoice or text. Provision of fields for descriptive inputs may be inaddition to or alternative to one or more predefined descriptivecategories and/or plurality of options within such descriptivecategories. In one embodiment, the ST application 700 may include orincorporate a photo application or otherwise be configured to input animage of a player. The ST application 700 may associate the image withthe player. In a further or another embodiment, the ST application 700is configured to analyze an image of a player and perform image analysisto extract descriptive attributes, such as color of an article ofclothing worn by the player. In this or another example, the STapplication 700 may display the picture of the player captured by thecompanion device or another device that transmits the picture, eitherdirectly or indirectly, to the companion device.

FIG. 7A depicts a user interface of the ST application 700 providing amenu 701 of selectable options according to one embodiment. Using theuser interface, the scorer may select player descriptions button 702from the menu 701. Upon selection of the player descriptions button 702,the user interface may display a player description screen 703 providingoptions for entering one or more player descriptions, e.g., as shown inFIG. 7B. In one configuration, the ST application 700 may pre-populateplayer names, such as those in a group the scorer is to track. In theseor other configurations the ST application 700 may provide a field intowhich the scorer may manually enter a player name or a selectable listof groups or players may be provided from which the scorer may select topopulate players to provide further description.

With reference again to FIG. 7B, the scorer may select a descriptionbutton 704 to provide a description for the player named VincentJohnson.

Selecting the description button may cause the ST application 700 todisplay one or more descriptive categories 705. In the example shown inFIG. 7C, the user interface displays a context box including a pluralityof descriptive categories 705 for selection by the scorer. The scorermay select a descriptive category from the available options and bepresented with a plurality of selectable descriptions. For example, inFIG. 7C, the scorer is presented with three descriptive categories 705related to articles of clothing: “player shirt”, “player pants”, and“player cap”. Selecting “player shirt” displays a plurality ofdescriptive characteristics 706 for a player shirt from which the scorermay select. The scorer may select a descriptive category that allows theplayers to be easily distinguished. For example, the scorer may selectone or more articles of clothing worn by a player that are distinct fromother players, to enable the scorer to distinguish which player ishitting a shot, even from a distance. Optimal descriptions may beprovided for instances where there may be a need to provide additionalclarity. In FIG. 7D, the descriptive characteristics relate to color. Inthis example, the descriptive characteristics also include additionalcharacteristics, identified as optional in this example, from which thescorer may further define the player shirt. In the illustratedinterface, the scorer has selected green for the color of the playershirt and light as an optional description. In some embodiments, such asthat illustration in FIG. 7D, the user interface may request that thescorer confirm the selections with a confirm button 707. The selectabledescriptive characteristics within the “Player pants” and/or “Playercap” may be similar or different than those within the “Player Shirt”descriptive category. While the descriptive categories relate to articleof clothing in the illustrated embodiment, in some examples differentdescriptive categories or descriptive characteristics may be provided,which may be in addition to or alternative to articles of clothing, suchas shoes, clubs, bag, brand of article, or the like.

In various embodiments, the ST application 700 may be configured toreceive the descriptive input with respect to one or more descriptivecategories. The number of descriptive categories to be defined by thescorer may be predetermined or specified in the ST application 700 ormay be left up to the scorer. As shown in the summary player detailsview 708 depicted in FIG. 7E, the scorer has also entered “black” for asecond descriptive category (player pants) for Vincent Johnson in thesame manner as described above with respect to FIGS. 7B-7D. FIG. 7E alsoillustrates that the scorer has entered descriptive characteristics fortwo descriptive categories (Player pants, Player cap) for playerMahindra Lutchman and one descriptive category (Player Shirt) for playerJarred Garcia.

The ST application 700 may be equipped with scoring features that enablescorers to enter a plurality of details with respect to play, includingclub type, shot location, strokes, penalties, scoring, lie, and thelike.

With reference to FIG. 7F, in some embodiments, the ST application 700may be configured to generate a club selection feature on the userinterface that a scorer may use to identify a club a player is currentlyusing to set up for and/or to strike a golf ball during play. Forexample, on the group screen 710, the scorer may select a “select club”button 709 associated with a player. At the tee, for instance, thescorer may select the “select club” button 709 and be presented with aselection of clubs 711, as depicted in FIG. 7G. The selection of clubsmay include any number of clubs, such as a player's full bag or anexhaustive list of potential clubs. In one embodiment, the selection ofclubs is programmed to correspond to those likely to be used by theplayer at the particular location of the course. For example, using thelocation of the companion device and/or the tracking module carried bythe player, the ST application 700 may determine a selection of clubs topresent that corresponds to those that players use in that or similarsituations and/or location on the course. In some embodiments, thelocation and/or situation may include zone determination, e.g., asdescribed with respect to FIG. 3 . For example, the location system maydetermine a location of the tracking module from location data providedto the location system wherein the location coordinates are applied topredefined coordinate ranges corresponding to defined zones to determinewhich zone the tracking module is currently located. In FIG. 7G, thescorer selects the “iron” button to indicate that the player is teeingoff with an iron on the par 3, second hole. In one embodiment, thecompanion device 12 will not respond to selection of a player namewithout the scorer first inputting a club. The club selection may bemade prior to the player arriving at the ball and/or before the playerstrikes the ball. While it is preferable that the scorer enters the clubprior to the player striking the ball, in some embodiments, the clubselection may be entered after the player strikes the ball.

The companion device 12 executing the ST application 700 may beconfigured to receive precise input of the player striking the ball. Insome embodiments, a “shot hit” button 712 may be provided that a scorermay tap the moment a player strikes the ball. To display the “shot hit”button 712 the scorer may select the name of the player from the groupscreen 710 (FIG. 7F) for which they will indicate the “shot hit”. Withreference to FIG. 7H, the user interface includes a “shot hit” button712 that the scorer will use to indicate a shot hit by pressing andholding their finger on the button prior to the ball being struck andthen removing their finger the moment the ball is stuck to indicate theshot. For example, when the player is addressing the ball, ready to makea shot, the scorer presses and holds the “shot hit” button 712. Then, atthe exact moment the player hits the shot, the scorer releases thebutton to indicate the shot has been hit. This action signals the systemto record the location of the tracking module at that moment, whichcorresponds to the location of the player. This location information maybe further associated with the club selection of the player. This datamay be saved in the tracking module, companion device or associatedmemory, or may be transmitted to a management device at that time, whenthe scorer indicates that the player or group has completed the hole,periodically, at scheduled intervals, based on proximity of the trackingmodule or companion device to a management device, or based on storagecapacity thereof. As described in more detail elsewhere herein, thelocation information may be input into an application configured torender graphical displays of digital stroke trails, detailing shots of around.

In some embodiments, when the scorer releases the “shot hit” button 712,the scorer is to subsequently input the landing location of the ballrelative to the golf course (e.g., fairway, rough, green, out-of-bounds,sand, hazard, area under repair, cart path, holed). The companion device12 may be configured to automatically display location choices when thescorer releases the “shot hit” button 712 or the user interface may beprovided with a location button the scorer may use to select from aplurality of locations or enter a location into a provided field. In theembodiment illustrated in FIG. 7I, upon release of the “shot hit” button712 the user interface displays an “in the hole” prompt 713 whereby thescorer may indicate whether the ball is in the hole. As shown, theinterface for the hole prompt 713 requires a direction swipe, left forno, right for yes. However, other interface buttons and methods may beused. After the scorer indicates whether the ball went in the hole, withreference to FIG. 7J, the user interface may return to the group screen710 that now displays the recorded shot. The group screen 710 may alsoinclude a notification or indicator 714 that the player is currently inplay on the hole. As shown, text below the player name has changed to“from location” indicating that the player is between shots on a hole.This indicator 714 may also operate as a button for triggeringcollection of location information of the tracking module when theplayer hits their next shot in a manner similar to that described withrespect to the first shot.

With reference to FIGS. 7K & 7L, to record the player's second shot, thescorer may select the “From Location button” 715 in the indicator 714from the group screen 710. This selection may cause a “From Location”screen 716 to be presented that includes a plurality of locations thescorer may select to indicate the location a player is hitting the shot.As shown, the scorer may select fairway bunker, fairway, first cut,native area, deep rough, water, greenside bunker, fringe, other, orgreen. As the player was not hitting their first shot, an option toselect “tee” is not available in this embodiment. However, selection of“provisional” or “penalty drop” will cause “tee” to be available.

In some embodiments, the course may be mapped prior to or after play andthe location of the recorded position of the tracking module,corresponding to the player and ball, may be overlayed on the map or theSTTM system may otherwise determine the location relative to the golfcourse based on the recorded location relative to the map. The coursemay be mapped using any coordinate or grid system and may utilize surveytechniques, global satellite constellation systems (GPS, GLONASS,BEIDOU, GALILEO & QZSS), LIDAR, or other suitable methodologies. Therecorded location information may be collected or converted directly orindirectly to such coordinate or grid systems and/or utilizing overlaytechniques.

After entering the from location on the “from location” screen 716, theuser interface may display the group screen 710. As shown in FIGS. 7M &7N, the location indicator 714 may change to that which the scorerselected, e.g., fairway. The scorer may then select the player name andto reveal the “shot hit” button whereby the scorer may indicate themoment the ball is hit by the player and then indicate if the ball wentin the hole, e.g., in a manner similar to that described above.

Recording the time and location of each player's putt may be performedin a similar manner to that described above with respect to other shots.In various embodiments, when the ball reaches the green, and the scorerselects “green” from the “From Location” screen, the location indicator714 on the group screen 710 may remain “green” until the ball is in thehole. In another embodiment, the user interface may allow a user toselect another location after subsequent shots that do not go in thehole, e.g., that may roll off the green. FIG. 70 illustrates a grouppage 710 wherein the first two players have finished the hole and thethird player is on the green. When it is the third player's turn toputt, the scorer may select the player's name, hold down the displayed“shot hit” button when the player is about to putt, and release when theplayer putts the ball to record the time and location of the putt vialocation of the tracking module as described with respect to FIG. 7H.The user interface may then display an “in the hole” prompt that thescorer may use to record whether the ball went in the hole, which may besimilar to that described with respect to FIG. 7I. If the ball did notgo in the hole, the scorer records the next putt as previously. If theball does go in the hole, the ST application 700 records the player asfinishing the hole and the scoring process starts again from the nexttee box. In one example, after the scorer records all the players in thegroup getting the ball in the hole. The location indicator 714 on thegroup page 710 may automatically revert to “select club”. In anotherexample, the user interface may prompt the scorer to indicate the holeis finished and to move to the next hole.

FIGS. 7P-7V Illustrate PDP scoring according to various embodiments. Inthese examples, the scorer records the “from location” on the “fromlocation” screen 716 where the next shot will be hit from, not where theoriginal shot landed. However, in some embodiments, the ST application700 or system may additionally provide an entry for landing location ofa previous shot by entry into a text field, selection from a list ofareas around the hole, such as “water” provided on the “from location”screen 716, or a map may be displayed and the scorer may indicate alanding location of the ball on the screen.

FIG. 7P illustrates recording a second shot off the tee recorded as aprovisional. Using the “From Location” screen 716, the scorer selects“Provisional” and then the from location, which is “tee” in thisexample. The display may then return to the group screen 710 and“Provisional” may appear as the location indicator. The scorer may thenselect the player's name and score the shot as described above.

With reference to FIG. 7Q, once the provisional shot is recorded,“Provisional” may remain in the location indicator 714 position underthe player's name until the scorer selects the player's name to recordthe location of the next shot. FIG. 7R illustrates a display prompt 720presented after selecting the player's name, requesting the scorer toindicate if the player is or is not using the provisional shot. If thescorer indicates that the player is not using the provisional shot,scoring will proceed as normal. If the scorer indicates that the playeris using the provisional shot, a penalty stroke is awarded, which may beindicated on the Group screen 710 as shown in FIG. 7S.

FIG. 7T illustrates recording a penalty drop. In some embodiments, whenrecording a penalty drop, the ST application 700 prompts the scorer toindicate the penalty drop ball is in play. For example, from the “FromLocation” screen 716, the scorer selects “Penalty Drop” and then thefrom location, which is “deep rough” in this example. The display maythen return to the group screen 710 and “Penalty Drop” may appear as thelocation indicator 714 under the player's name, FIG. 7U. The scorer maythen select the player's name before the player drops the ball. Forexample, with reference to FIG. 7V, the scorer is presented with apenalty drop prompt 721 providing a “ball in play” button 722 that thescorer uses to indicate when the player drops or re-tees the ball. Thisassesses a penalty stroke and further shot location and time maycontinue to be recorded as described above.

A free drop may be recorded in a manner similar to that of recording apenalty drop, except “penalty drop” is selected from the “From Location”screen and a penalty is not accessed.

With reference to FIGS. 8A-8G, in various embodiments, the STTM systemincludes a data management system 50 configured to review and editscoring data recorded by the score tracking system. The data managementsystem 50 may provide data managers data access to management operationslocally, remotely, and/or from any location via management devices.

The data management system 50 may include a data management tool 800including one or more elements, e.g., interface elements, displayelements, or associated operational elements, selected from an (a) eventselector 801, (b) a round selector 802, (c) a course selector 803, (d)an edit mode notification 804, (e) a data discrepancy panel 805, (f)hole graphic representation 806, (g) a group scorecard 807, (h) a teamplayer stroke detail 808, or (i) an all group presentation 809. FIG. 8Adepicts an example user interface of the data management tool 800 foruse with the data management system 50 providing the elements listedabove in presentation blocks. In various embodiments, the page layout ofthe elements is configured to enable connections to be created betweenblocks and/or data elements therein. For example, when selecting anelement in one block, connections may be established for other blocks.In a further example, the other blocks in which connections areestablished may be updated with an appropriate presentation, asdescribed in more detail below. However, it will be appreciated that theelements and the associated components and data thereof operable toprovide the operations of the data management system 50 may be providedin many formats and the present disclosure is not limited to theparticular arrangements and combination of elements and user interfacecomponents depicted herein.

The event selector 801 may include a selectable listing of one or moreevents available for viewing and management of the associated data. Inone example, the event selector 801 comprises a drop down list of allevents that are available for viewing. Selection of an event may causethe presentation blocks to present or be operable to present theassociated data for that event.

The round selector 802 may include a selectable listing of one or morerounds of an event available for viewing and management of theassociated data. In one example, the round selector 802 comprises a dropdown list of all available rounds for the event selected with respect tothe event selector component. In a further example, selection of a roundmay cause the presentation blocks to present or be operable to presentthe data for the round of the event selected. In a further example, theround selector 802 and/or presentation blocks may default to the mostrecent round in progress. If no rounds are in progress, the default maybe the earliest round having a “grouping official” round status, asdescribed in more detail with respect to the round management system 60.

The course selector 803 may include a selectable listing of one or morecourses for the event and round selected that are available for viewingand management of the associated data. In one example, the courseselector 803 comprises a drop down list of all courses that areavailable for the selected event and round. Selection of a course maycause the presentation blocks to present or be operable to present thedata for the course of the event and round selected. In one example, adefault course may be set to a host course when multiple courses arebeing played for an event and round. In another or a further example,the course selector 803 may include a selectable option to select allcourses. In one such example, selection of all courses causepresentation of the data for all courses in the presentation blocks inone combined presentation.

The edit mode notification 804 may include a display element comprisinga notification that is presented when an edit has been made in any ofthe presentation blocks that scoring data has been edited. The edit modenotification 804 may be selectively programmable to providenotifications with respect to any desired edit. For example, in someembodiments, the notification is not displayed when changes are madeonly to play management blocks, described below. In one example,notifications are output when data element values are above or below apredefined threshold or within or outside a predefined range. Thenotification may be interactive such that a user may interact with thenotification, such as select all or a portion of the notification, toaccept the changes. In one embodiment, a separate interface element isprovided that a user may interact with to accept the changes. In someconfigurations, the notification may display or be operable to present asummary or identification of the changes causing the notification.

In various embodiments, when a user changes or enters data into thepresentation blocks, the data management tool 800 may be automaticallyplaced in an edit mode. While in edit mode, the data may not betransmitted to downstream clients or data viewing platforms thereof.However, when a user accepts all the current edits, edit mode may beturned off and the data, including any changes made while in edit modemay be sent to downstream clients, including data viewing platformsthereof.

The hole graphic representation 806 may be provided in a 2D graphic(although more advanced graphics such as 3D may also be used). The holegraphic representation 806 may include various navigationfunctionalities. For example, the hole graphic representation 806 mayinclude one or more of a zoom functionality allowing a user toselectively zoom in and out of the graphic; a graphic rotationfunctionality allowing a user to selectively rotate the graphics on ahorizontal axis, vertical axis, and/or other axes; and/or a variablecentering functionality allowing a user to move the center of thegraphic in the presentation panel. In one example of a zoomfunctionality, a quick zoom may be provided to zoom into the green, zoomout to display an entire hole, and/or zoom out to display the entirecourse. In one example, the graphic is oriented in a method that allowsmaximum viewing from tee to green, such as an overhead view, tee view,or green view. The hole graphic representation may include variousdisplayed distances with respect to the hole. For example, one or bothof a scorecard yardage distance or an actual yardage distance betweenthe tees and pins as set for the round may be displayed. In oneconfiguration, hole setup information may be displayed on the holegraphic. For example, current hole information may be displayed for eachround, such as one or more of tee locations, pin locations, and/orcenter of fairway points for the holes of the course. In one embodiment,the graphic presentation may be configured to show all players of agroup at one time upon request from the user, e.g., via interaction witha “show all group players” element.

Stroke or ball position coordinates, such as those collected via theoperations of the tracking module and companion device, may be plottedon the hole graphic representation 806. For example, the hole graphicrepresentation 806 may include plots of ball positions relative to thehole. For example, ball position may be plotted in the graphicpresentation to show the ending position of a team player's stroke. Fora consecutive stroke containing location coordinates, a line may bedisplayed between the plotted points to depict a stroke trail. As thestarting point is the tee and the ending point is the pin, the datamanagement tool 800 may generate lines from these points to strokes withthe coordinates or ending positions of the player's strokes on the hole.In one example, distance of plotted ball positions from the tee,distance from the last stroke, and/or distance to the pin may bedisplayed or provided as a defined selectable format option.

Additional functionalities may be provided for managing coordinates fora stroke, such as enabling a user to enter a location for a strokereceived; move an existing location assigned to a stroke; create astroke along with a location for the stroke; displaying all GPS or otherlocation coordinates collected for a team player, and/or delete a strokealong with its location. In an example of the above functionalities,where breadcrumbs are present, the hole graphic representation 806 maybe configured to enable a user to “lock” a stroke to a breadcrumb.

In one embodiment, the functionalities include displaying all GPS and/orother coordinates collected for a team player including ones notassociated with a stroke, e.g., breadcrumbs. With the presentation ofall coordinates, the hole graphic representation 806 may be configuredto associate one location to a stroke of a player.

In various embodiments, selecting a group from the all grouppresentation 809 may cause the group scorecard 807 to populate with thedata associated with the group. In one example, the hole graphicrepresentation 806 may similarly populate with shot and/or ball positiondata related to the group. In one example, selecting specific holes of agroup via the group scorecard 807 causes the hole graphic representation806 to zoom to the selected hole and display plotted ball positions andshot trails of the team players in the group.

FIG. 8B illustrates an example interface 810 of the group scorecard 807that may be presented by or accessible via interaction with the groupscorecard data management tool 800, all or a portion of which may beavailable in the respective presentation block view. Various elements ofthe group scorecard 807 may be displayed and/or editable via operationand functionalities of the group scorecard 807, as described in moredetail below with respect to the respective elements. The groupscorecard 807 may include various data elements such as one or more of(a) team player name 811, (b) stroke event 812, (c) stroke count 813,(d) total 814, (e) total 815, (f) today 816, (g) front nine hole by holescores 817, (h) score out 818, (i) back nine hole by hole scores 819,(j) score in 820, (k) stroke total, or (l) strokes official 821.

Team player name 811 may list the team players in a group. For example,the players may be presented by last name, first name. In oneconfiguration, team player name 811 may not be edited via the groupscorecard component of the data management tool 800.

Stroke event 812 may present the last stroke event that has beenreceived from the score tracking system or, in one example, thevalidation system if flagged. Various stroke events may be presented,such as club selection, addressing the ball, shot hit, provisional,preliminary, final, and in the hole. In one configuration, stroke event812 may not be edited via the group scorecard component of the datamanagement tool 800.

Stroke count 813 may be a representation of strokes currently recordedfor the hole that the player is on. If a team player has not startedtheir round, the stroke count may default to show the starting tee time.In one configuration, stroke count 813 may not be edited via the groupscorecard component of the data management tool 800.

Total 814 may present the total par relative score for the event. In oneconfiguration, total 814 may not be directly edited via the groupscorecard component of the data management tool 800.

Today 815 may present the par relative score for the round. In oneconfiguration, today 815 may not be edited via the group scorecardcomponent of the data management tool.

Front nine hole by hole scores 816 may present a list of scores by holefor the first nine holes. In some embodiments, a column or row header,dependent on configuration, may be provided to show the hole numbers forimproved clarity. In one configuration, front nine hole by hole score816 may be edited via the group scorecard component of the managementtool 800 by entering an integer or removing a score from a hole scorefield.

Score out 817 may present a stroke total for the scores entered on thefront nine. In one configuration, score out 817 may not be directlyedited via the group scorecard component of the data management tool800.

Back nine hole by hole scores 818 may present a list of scores by holefor the back nine holes. In some embodiments, a column or row header,dependent on configuration, may be provided to show the hole numbers forimproved clarity. In one configuration, back nine hole by hole score 818may be configured to be edited via the group scorecard component of themanagement tool 800 by entering an integer or removing a score from ahole score field.

Score in 819 may present a stroke total for the scores entered on theback nine. In one configuration, score in 819 may not be directly editedvia the group scorecard component of the data management tool 800.

Stroke total 820 may present a stroke total for the round. In oneexample, the stroke total 820 may be displayed only when score out 817and score in 819 have been populated with data. In one configuration,score total 820 may not be directly edited via the group scorecardcomponent of the data management tool 800.

Strokes official 821 may present the strokes received for the teamplayer on all holes that are flagged as official. In one configuration,this element can be edited by the user to signify that no more editswill be conducted for any strokes on any holes for the player.

FIG. 8C illustrates an example interface of the team player strokedetail 808 of the data management tool 800 configured to interface auser with the operations thereof. The interface may be presented in oraccessible via interaction with the team player stroke detail 808element of the respective presentation block view of FIG. 8A. Elementsof the team player stroke detail 808 may be displayed. In operation ofthe team player stroke detail 808 a user may be enabled to edit variouselements. In some embodiments, selecting a player in the group scorecard807 or all group presentation 809 populates the interface of the teamplayer stroke detail 808 with the respective data elements of theselected group.

When selecting a team player for presentation and/or stroke editing withthe team player stroke detail 808, the hole graphic representation 806may default to display a course view, a current hole, next hole, firsthole completed, last hole completed, or full course view. In oneembodiment, selection of a particular hole from the group scorecard 807,e.g., by selecting a hole from the front nine hole by hole 816 or frontnine hole by hole 818 (FIG. 8B) data element views, causes the teamplayer stroke detail 808 to present the stroke detail for the player forthe particular hole. Thus, the data management tool 800 may beconfigured to enable a user to selectively view strokes by hole with thegroup scorecard 807 or stroke detail for a hole via interaction with theteam player stroke detail 808.

In one example, viewing stroke detail for a team player with respect toa hole via the team player stroke detail 808 causes the hole graphicrepresentation 806 to present a representation of the hole. The graphicmay be oriented from left to right with the tee location being on theleft side and the green on the right side. As noted above,functionalities such as zooming into and out of the graphic may beprovided. In one example, a quick zoom operator may be provided to allowa user to quickly zoom to various areas of the hole, such as tee box,fairway, hazards, green area, or to a particular selected shot. Thefunctionalities may also include moving the graphic to change thelongitude and latitude of the view within a static viewing area, e.g.,within any zoom value. Yardage distances may also be displayed withrespect to the set positions of the tees and pins. Other yardages may beselectably presented in or relative to the graphic as described above.

The data elements of the team player stroke detail 808 may includevarious informationals and scoring data elements such as one or more of(a) team player name 822, (b) stroke number 823, (c) strokes accessed824, (d) stroke event 825, (e) time stamp 826, (f) stroke type 827, (g)location 828, (h) club 829, (i) provisional 830, or (j) in the hole 831.The data elements may correspond to those collected by the STapplication via operation of the companion device described herein. Suchdata elements may be received by the data management system 50 forviewing and/or editing.

Team player name 822 may include a list of all team players in a group.For example, selecting a group from the all group presentation 809 orthe group scorecard 807 may cause the team player name 822 to populatewith the team players of the group. The presentation may display datawith respect to a single player, which may be defaulted to any player,such as the last player with a recorded stroke event or to havecompleted a hole, the first player in the predefined order of teeingoff, or the like. In one configuration, the team player name 822 may notbe edited via the team player stoke detail 808.

Stroke number 823 may correspond to a stroke received. In oneconfiguration, the stroke number 823 is editable via the team playerstoke detail 808, allowing a user to enter an integer.

Strokes accessed 824 may correspond to a number of strokes that willcount towards the hole score for a team player on that stroke received.In one configuration, the stroke accessed 824 is editable via the teamplayer stoke detail 808, e.g., allowing a user to enter an integer.

In one embodiment, a user may create a stroke before or after any otherstroke. If a stroke is created, the data management tool 800 may beconfigured to automatically set the stroke number as the number afterthe previous stroke. If a stroke is created between two other strokes,the other strokes following the created stroke may be automaticallyrenumbered, starting from the stroke created. The data management tool800 may edit the timestamp 826 to be set to a time either after theprevious stroke or a time before the proceeding stroke. In one example,when a stroke is created, the default strokes accessed are one.

In one embodiment a user may delete a stroke. If a stroke is deleted,the data management tool 800 may be configured to automatically renumberthe remaining strokes in sequential order. If a stroke is deleted and itis not the stroke within the hole 831 being flagged but rather a strokewhere the “in the hole” flag is available, the data management tool 800may recalculate the score with the new sum of strokes accessed. If thestroke with the “in the hole” flag is deleted, the data management tool800 may be configured to clear the score calculated. As described below,the “in the hole” flag may be set or removed by the user. Followingdeletion of a stroke including the “in the hole” flag, the user may setthe “in the hole” flag for another stroke from which a revised score iscalculated by the data management tool 800. In one example, the user maybe prompted to flag a stroke with the “in the hole” flag upon deletionof a stroke flagged as “in the hole”.

Stroke event 825 may correspond to the latest stroke event received.Stroke event 825 may enable a user to identify a stroke event. Thus, inone configuration, the stroke event 825 is editable via the team playerstroke detail 808. Editable options may be provided and may include oneor more event types selected from club selection, addressing the ball,shot hit, preliminary, final or in the hole, corresponding to suchevents collected by the ST application via the companion device andtracking module.

Time stamp 826 may correspond to that of a stroke event 825, such as thelatest stroke event 825. In one configuration, the time stamp iseditable via the team player stoke detail 808, allowing a user to editthe field in a format of a time and day entry.

Stroke type 827 may correspond to a stroke type identifier, such asstroke, penalty, or drop, corresponding to such stroke types collectedby the ST application via the companion device. In one configuration,stroke type 827 is editable by the data management tool 800 to change oradd a stroke type from a list. In one example, interacting with stroketype 827 causes a dropdown to appear including a list of availablestroke types enabling the user to select one of the stroke types to set.In various embodiments, the data management tool 800 may automaticallyapply various rules to edits of stroke type. For example, if a stroketype created is “drop”, the strokes accessed 824 may be zero. If astroke type created is “drop”, the stroke number 823 may be the same asthe previous stroke or penalty type. If a stroke type created is“penalty”, the strokes accessed 824 may be defaulted to one. If a stroketype created is “penalty”, the stroke number 823 may increment to anamount identified for strokes accessed 824.

Location 828 may correspond to a graphic location of the stroke asdetermined by location methodologies described herein, e.g., viaoperation of the tracking module, location system, rangefinder, manualentry via indicating a location of ball positions relative to adisplayed map, or other location methodology used by the STTM scoringsystem. In one configuration, location 828 is editable to change alocation from an available list of location descriptions for the golfcourse being played, e.g., tee box, fairway, rough, first cut, hazard,water, out of bounds, green, or the like. In one example, interactingwith the location data element may cause a dropdown to appear includinga list of available locations for the golf course that may be set forlocation.

Provisional 830 may be used to identify if a stroke is a provisional ornot. In one configuration, the provisional field is editable with valueoptions of “yes” or “no” with respect to if the stroke is a provisionalstroke.

In the hole 831 may be used to identify if the specified stroke resultedwith the ball in the hole or not. In one configuration, a user may setor remove a flag if the stroke is considered to be in the hole. The datamanagement tool 800 may automatically apply various rules to “in thehole” flags. For example, if the last stroke with the highest strokenumber is flagged “in the hole”, a score may be calculated and storedbased on the sum of all strokes accessed. If a stroke that is not thelast stroke with the highest stroke number is flagged “in the hole”,that stroke is set as the highest stroke number and all other strokesmay be renumbered in sequential order.

With reference to FIG. 8D, in various embodiments, a stroke event reviewviewer 832 may be provided. For example, each stroke in the playerstroke detail 808 may be operable to be optionally expanded out to showadditional associated stroke events. In the illustrated viewer, strokeevents for a stroke are populated in the stroke event 823 element. Asshown, the stroke events for the stroke number include club selection,addressing, shot hit, preliminary, and final. Thus, the stroke did notresult in the player holing the ball. In various embodiments, strokedetails received from companion devices may be marked “preliminary” andbe subject to review via operation of the data management tool 800 orvalidation system described below, successful review of which may setthe stroke detail to “final”. In one configuration, the fields of thestroke event review viewer 832 cannot be edited except for the timestamp field. The stroke event review viewer 832 may be configured toenable a user to reorder or sort stroke events in the sequence ofevents. The stroke event review viewer 832 may be configured to enable auser to collapse the review of stroke events, such as to just presentingthe latest stroke event.

FIG. 8E illustrates an example interface of the all group presentation806 of the data management tool 800 configured to interface a user withthe operations thereof. All or a portion of the interface may bepresented in the respective presentation block view of FIG. 8A or may beaccessible via interaction with the all group presentation 806 thereinprovided. Various elements of the interface may be displayed and/oreditable via operation of the all group presentation 806.

The all group presentation 809 may be configured to display a selectedround, which may include displaying only the selected round. In oneexample, the all group presentation 809 is configured to display acourse selected or information for all courses of a tournament, ifselected. In some configurations, the display may be scrollable and/oreach column of data may be sorted in either ascending or descendingorder based on the information available in the column. In oneconfiguration, none of the fields in the all group presentation 809 maybe directly edited via the all group presentation 809. In oneembodiment, the presentation of the all group presentation 809 mayinclude a notification with respect to a team player's name if the teamplayer's scorecard has been flagged as “official”, e.g., via avalidation system described in more detail elsewhere herein.

The all group presentation 809 may include various data elements, suchas one or more of (a) group number 832—corresponding to a numberassigned to the group; (b) course 833—corresponding to course the groupnumber is playing; (c) starting hole 834—corresponding to first holethat the group started on, based the groupings for the round; (d) teetime 835—corresponding to the starting tee time of the group; (e) rank836—corresponding to the projected rank of the player during theprogress of play during rounds in progress; (f) team player name837—corresponding to identification of the player; (g) total838—corresponding to the current total par relative score for the event.(h) today 839—corresponding to the par relative score for the round; (i)front nine hole by hole scores 840—corresponding to a list of scores byhole for the first nine holes; (j) score out 841—corresponding to astroke total for the scores entered on the front nine; (k) back ninehole by hole scores 842—corresponding to a list of scores by hole forthe back nine holes; (l) score in 843—corresponding to a stroke totalfor the scores entered on the back nine; or (m) stroke total844—corresponding to a stroke total for the round, which display whenthe score out 841 and the score in 843 have data.

FIG. 8F illustrates an example interface of the data discrepancies panel805 of the data management tool 800 configured to interface a user withthe operations thereof. All or a portion of the interface may bepresented in the respective presentation block view of FIG. 8A or may beaccessible via interaction with the data discrepancies panel componenttherein provided. Various elements of the interface may be displayedand/or editable via operation of the data discrepancies panel 805.

The data discrepancies panel 805 may include two sub-elements comprisingan error message panel 850 and warning message panel 851. In oneembodiment the sub-elements may be configured to function independently.

In various embodiments, the data discrepancies panel 805 may bemanipulated to enhance user experience and efficiencies. For example,the rows of data may be scrollable. The columns of data may also besortable in either ascending or descending based on the informationavailable in the column. In one configuration, the data discrepancypanel 805 may provide an interface element operable to flag a warning asreviewed and to remove the warning from the presentation. In oneexample, the data discrepancy panel 805 may enable a user to review allwarnings that have been flagged as reviewed; review errors and warningeither by group, hole, or team player; reset and display all errors andwarnings if anything has been set as reviewed and removed; scrollthrough all messages by panel if they are not viewable in the initialdisplay; or to turn on or off the rules for all or select error and/orwarning message rules. In one example, none of the fields may be edited.

In various embodiments, error message 853 and warning message 854 mayidentify various identification elements with respect to the player,time, and/or location to which the message relates. In the illustratedembodiment a team player name 855, hole number 856, and group number 857data elements are presented. The data management tool 800 may beconfigured to analyze scoring and/or location data and associatedprocedures and automatically generate error and/or warning messages 853,854 when anomalies are identified.

Error messages 853 may relate to missing data and/or proceduralanomalies with respect to recorded score and/or location data, which maybe displayed in the error message 853 element associated with theidentifying information. Various error messages may be included, such asone or more of missing location description; missing coordinates on astroke; missing scores, which may be displayed, for example, if thereare scoring gaps between holes; strokes accessed does not sum up to thescore recorded; score recorded but there are no strokes; no penaltyrecorded for a stroke flagged as provisional with strokes accessed ofone; non-sequential timestamps for stroke trails from hole to hole;first stroke is not from the tee location; a stroke is not flagged asfinal after receiving the next stroke; or a team player is not markedstrokes official after the team player has completed the round.

Warning messages 854 may relate to events or lack thereof detected bythe data management tool 800 that may not yet be errors or that cannotyet be confirmed to be errors based on the available data but that areanomalous compared to expected operation of the scoring system, whichmay include the location system. Warning messages 854 may be displayedwith associated identifying information. Various warning messages 854may be included, such as one or more of players being tracked is out ofsync with strokes of the other team players in a group; multipleconsecutive drops for a team player; drop without a penalty in a teamplayer's stroke trail; stroke's coordinates are not closer to the pinlocation than the previous stroke's coordinates; more than 10 minutesbetween strokes for a team player; multiple strokes contain a locationfrom the tee; non-typical score for a team player, such as double bogiesor worst and eagles and better; 5 minutes have elapsed and a stroke hasnot received coordinates; team player was on the green then appears tobe off the green; driving distance is out of range of a normal distanceon a par 4 and 5, such as less than 180 yards and longer than 380 yards;a stroke was flagged as in the hole that had a distance greater than 30yards; pin has not been set and a stroke for a team player has beenreceived on that hole; or tee has not been set and a stroke for a teamplayer has been received on that hole.

With reference to FIG. 8G, in various embodiments, the presentationblock of the data management tool 800 and/or one or more associatedcomponents thereof described above with respect to FIGS. 8A-8F, may beconfigured to create connections therebetween. For example, thepresentation block layout may be configured to create a connectionbetween blocks views of the component elements. For instance, whenselecting an element or otherwise interacting, e.g., making a selection,in one block view or otherwise with respect to an associated element, aconnection is established for one or more other blocks to thereby updatethe appropriate presentation in the respective blocks.

The presentation block may be configured to apply connection rules withrespect to the all group presentation 809. In one example, selecting ateam player's name causes one or more of the group scorecard 807 topresent the group the team player is in; the hole graphic representation807 to present the current hole the team player has not completed; theteam player stroke detail 808 to present the strokes received on thecurrent hole the team player has not completed; the data discrepanciespanel 805 to present all the errors and warnings for the team playerselected on all holes. In the above or another example, selecting agroup number may cause one or more of the group scorecard 807 to presentthe group selected; the hole graphic representation 806 to present thecurrent hole and defaults to the top team player in the group and thecurrent hole the team player has not completed; the team player strokedetail 808 to display the strokes received on the current hole the topteam player in the group has not completed; or the data discrepanciespanel 805 to present all the errors and warnings for the group selected.In any of the above examples or another example, selecting a hole of ateam player may cause the group scorecard 807 to present the group theteam player is in; the hole graphic representation 806 to present theteam player selected and the hole selected the team player stroke detail808 to present the strokes received on the hole and team playerselected; or the data discrepancies panel 805 to present all the errorsand warnings for that hole and team player, which may include anywarnings that have been flagged as reviewed.

In any one of the above embodiments or another embodiment, interactionwith the group scorecard 807 may cause connections with one or moreother components of the data management system 50. For example,selecting a team player's name may cause one or more of the hole graphicrepresentation 806 to present the current hole the team player has notcompleted; the team player stroke detail 808 to present s the strokesreceived on the current hole the team player has not completed; the datadiscrepancies panel 805 to present all the errors and warnings for theteam player selected on all holes; or the all group presentation 809 topresent the group or team player at the top of the presentation. In afurther or another example, selecting a hole of a team player may causeone or more of the hole graphic representation 806 to present the teamplayer selected and the hole selected; the team player stroke detail 808to present the strokes received on the hole and team player selected;the data discrepancies panel 805 to present all the errors and warningsfor that hole and team player, which may include any warnings that havebeen flagged as reviewed; or the all group presentation 809 to presentthe group or team player at the top of the presentation.

In any one of the above embodiments or another embodiment, interactionwith the team player stroke detail 808 may cause connections with one ormore other components of the data management system 50. For example,selecting a stroke may cause a location coordinate in the hole graphicsrepresentation 806 to be presented if a coordinate for the stroke ispresent.

In any one of the above embodiments or another embodiment, interactionwith the hole graphic representation 806 may cause connections with oneor more other components of the data management system 50. For example,selecting a location coordinate that is assigned to a stroke may causethe stroke selected in the team player stroke detail component to behighlighted.

In any one of the above embodiments or another embodiment, interactionwith the data discrepancies panel 805 may cause connections with one ormore other elements of the data management system 50. For example,selecting an error or warning to be reviewed may cause the presentationof the group scorecard 807 to be updated based on the team player andthe group identified in the error or warning message. In another or afurther example, selecting an error or warning to be reviewed may causethe presentations of the hole graphic representation 806 and/or teamplayer stroke detail 808 to update based on the team player identifiedin the error or warning message.

In various embodiments, STTM system includes a validation system 70configured to provide streamlined validation of a player's officialscorecard against scores collected by the score tracking system. Thevalidation system 70 may be configured to allow users to make changes tothe scores obtained from the operation of the score tracking system, ifnecessary. Using the validation system 70, users may also quicklyidentify a scorecard as reviewed and flagged as official. In someembodiments, this official designation may be transmitted or otherwiseimmediately available on one or more data platforms to communicate tousers of the scoring data that no more score edits will be received forthe respective player. In one example, the validation flagging of ascorecard as official is retained for archiving in a database, laterdissemination, internal verification, compiling with additionalvalidated scorecards, analysis, or combination thereof.

The validation system 70 may be configured for operation in variousnetwork environments, such as those identified herein with respect tothe various STTM systems/subsystems thereof. For example, the validationsystem 70 may be configured for operation in local, remote, ordistributed network based environment. The validation system 70 may beconfigured for operation in a web-based, cloud-based, or other suitablenetwork environment. In one embodiment, the validation system 70 mayoperate within a browser or browser-like environment. For example, thevalidation system 70 may include a validation application that has theability to run on multiple browser tabs with different settings. In afurther example, the validation system 70 includes an edit trackingfeature wherein the validation system tracks edits by user. These useredits are tracked as being associated with the particular user makingthe edits. The tracking feature of the validation system may beconfigured to store the tracked edits by user and make the tracked editsreviewable. For example, a reviewing user may access the validationsystem 70 and view a list of users and review details regarding editseach user made to which scorecards. In some configurations, thevalidation system 70 may allow a reviewing user to view edits of a userby type, such as score, stroke, location, stroke type (drop, shot,penalty), etc.. In this or another configuration, the validation system70 may be configured to allow a reviewing user to view edits by one ormore types by one or more or all users within a particular time periodor event.

With reference to FIG. 9A-9B, in one embodiment, the validation system70 may be configured to generate two functional validation tools forscorecard validation. Each validation tool may be provided in one ormore tabs, screens, pages, windows, or any suitable displayablearrangement having the functionality described herein. The validationtools may be separately displayed or displayed together, in whole or inpart. In one example, a first tool panel may be configured for entry ofplayer scorecard scoring data and comparison with a second scorecollection methodology, such as an automated or semi-automated scoringmethodology. The operations of the first tool may be referred to hereinas blind validation. A second score collection methodology according tovarious embodiments is described below with respect to the trackingsystem methodology, but it is to be appreciated that variations of thisscore collection methodology or other score collection methodologies maybe similarly applicable to the operations of the validation system.Thus, the first validation tool may be configured for blind validationthat allows a user to enter scores for a player's scorecard, wherein theentered scores are automatically compared against the scoring datarecorded by the score tracking system. The second validation tool maygenerate an output of all scores of players of a particular group, allgroups, all players, or desired combinations thereof together with theplayer rankings. In various embodiments, the validation tools may bearranged in selectable tabs, wherein each tab includes a validation toolwithin a panel.

FIG. 9A illustrates an example first validation tool 901 configured forblind validation.

An event selector 902 may be provided to allow users to select the eventthat the validation system 50 will use for player scorecard validation.The event selector 902 may include a listing of selectable events.Interfacing with the event selector 902 may cause a dropdown, listing,or other selectable format of events for selection.

A round selector 903 may be provided to allow a user to select a roundthat the validation system will use for player scorecard validation. Insome embodiments, event selection may be a prerequisite to roundselection. For example, if the event is not static, known. or otherwiseentered, the validation tool 901 may not allow the user to interact withthe round selector 903. Interaction with the round selector 903 maycause the available rounds for the event to be presented for selection,which may be in a manner similar to that described with respect to theevent selector 902. In one example, after a user selects the event, thevalidation tool 901 generates a selectable list of the available roundsfor the event in the event selector 902.

A cut line 904 may be provided to allow a user to view a display of thecurrent, real time cut data. In some embodiments, the cut line 904 isonly presented when the selected round is a cut round. Viewing the cutline 904 may provide a user insight with respect to what a modificationmay do relative to the cut. For example, changing one player's scorecould result in several other players making/missing the cut.

A group selector 905 may be provided to allow a user to select a groupincluding players for scorecard validation.

A player selector 906 may be provided that includes a list of selectableplayers in the selected group. In one embodiment, a player selector 906is provided without a group selector 905 wherein a list of participatingplayers is provided from which a user may select.

The name of the player that is currently being reviewed for scorecardvalidation may be displayed in a player name 907 field. In someconfigurations, an image, such as a headshot, of the player may bedisplayed.

A score entry may be provided for entering the player's score from theplayer's scorecard. The score entry may include hole fields 910 forentry of scores from all holes of the round, e.g., 18 hole fields. Thehole fields 910 may be configured for manual entry. In one example, thehole fields 910 include dropdowns for each hole with selectable scores,toggle fields, or other suitable entry methodology. In the illustratedembodiment, the score entry includes hole fields 910 that require a userto cause each field to be available for entry, e.g., using the enter keyor tab to select a hole field 910, along with a mouse navigation. Asnoted below, scores received by the validation system 70 that wererecorded by the score tracking system may be absent or otherwiseobscured from view such that the manual score entry and subsequentcomparison with the score tracking system score is blind from the user'sperspective.

System received scores, such as those received from score trackingsystem, may be imported into the validation system 70. In someembodiments, the importation of score tracking system scores may beautomatic upon receipt of the scores or may be delayed. The score dataand associated player data may be imported into the validation systemafter each hole is completed, periodically, when received, after apredetermined number of holes, or when the player or group has finishedthe round, which may be indicated by the scorer via the companiondevice. For example, when a scorer indicates a player or group hascompleted a hole or round, the calculated score and player name ornumber associated with the data may be sent directly or indirectly tothe validation system. In the illustrated embodiment, if the scorecardhas not been flagged official on a player that is selected, the systemreceived scores will not be visible or will be blank while the userenters the scores for purposes of blind validation.

In the illustrated example, the first validation tool 901 includes acompare trigger 912 to cause comparison between the scores. For example,with respect to blind validation, a user may interact with the comparetrigger 912 to initiate the comparison between the player scorecard andsystem received scores to be validated. Prior to triggering thecomparison, the first validation tool 901 may not display the systemreceived scores. In some embodiments, comparison may be initiated uponentry of one or all scores or upon population of the system receivedscores, which may be provided as a button or other interactive trigger.

As a result of the compare operation, system received scores maypopulate in hole fields 914 juxtaposed to corresponding hole fields 910.Validity notifications may be displayed with respect to a hole orassociated score to indicate score matches, score discrepancies, orboth. For example, when the option to compare blind entry scores versussystem scores is triggered, the system scores may appear and validnotifications of what matches and what does not match may be displayed.In the illustrated embodiment, solid arrows 918 between the blind scorehole fields 910 and the system received score hole fields 914 indicatethat the scores match while broken arrows 920 indicate discrepancies.The validity notifications may be provided by any suitable indicia. Forexample, matches and/or discrepancies may be indicated by differentcolors, shading, text, outlines, boxes, symbols, or other suitableperceivable indicia.

The first validation tool 901 may include an official marker 922 thatallows a user to flag the scorecard as official. For example, if theblind validation indicates that all the scores match, the user mayinteract with the official marker 922 and mark the scorecard asofficial. In another example, the validation system 70 may automaticallyflag the score as official if all the scores match.

In some embodiments, scores may be editable by users to resolvediscrepancies. In one configuration, scores with discrepancies or editedscores are sent or saved for additional review. As noted above, markingthe scorecard as official may transmit the scorecard, score, or officialflag to a database for storage and/or dissemination to one or more dataplatforms with an indication that the score is official. In someembodiments, scores recorded by the score tracking system may betransmitted to one or more data platforms as an unofficial score, andflagging the score as official via the validation system causes thevalidation to be transmitted to the data platforms to indicate the scoreis now official.

In one embodiment, after a blind comparison has been triggered, the useris given the ability to edit any score in the system scores scorecard.In this or another example, the ability to mark a player's scorecard asofficial is prevented until all score discrepancies have been resolved.In the above or another example, a notification may be displayed for theplayer's scorecard associated with the validation system 70 when it hasbeen marked official, and the notification remains on the player'sscorecard if the user navigates off and back to the player.

With reference to FIG. 9B, the second validation tool 830 may presentscoring data for one or more groups. The presentation may be configuredto display the scores from the event and/or round selected, such as thatselected with respect to the first validation tool 901. The scorespresented may include unofficial tracking scores and official scores. Asdescribed elsewhere herein, various score transmission timing schemesmay be used. In various embodiments, tracked scores may be populatedwhen transmitted companion devices 12, such as after each shot hit entryor when a player or group completes a hole.

The scoring data may be arranged in various formats. In the illustratedembodiment, the scoring data is arranged such that each column of datais sorted either in ascending or descending order based on theinformation available in the respective column. The fields willtypically not be editable from a basic user standpoint. The display maybe scrollable to view groups other than those initially displayed. Inone example, selecting a player or group will populate that player orgroup with respect to the second validation tool. Thus, a user mayselect a player or group and view additional details regarding theplayer's or group's scores. In one example, if the manual score entryhas not been entered or processed through validation, selecting theplayer or group will populate the group selector and/or player selectorfields to the selected player or group. In one embodiment, playershaving scores marked as official are marked with visual indicia as anotification of the same.

The presented scoring data may include various data points with respectto the players and scores such as one or more of (a) group number931—corresponding to the group number assigned to the group of players;(b) course of play 932—corresponding to the course the scoring data wascollected; (c) starting hole 933—corresponding to the first hole thatthe group started on based the groupings for the round; (d) tee time934—corresponding to the starting tee time for the group; (e) rank935—projected rank of the player during the progress of play duringrounds in progress, (f) team player name 936—corresponding to the lastname and first name of each team player in the group; (g) total937—corresponding to the current total par relative score for the event;(h) today 938—corresponding to par relative score for the round; (i)front nine hole by hole scores 939—corresponding to a list of scores byhole for the first nine holes; (j) score out 940—corresponding to stroketotal for the scores entered on the front nine; (k) back nine hole byhole scores 941—corresponding to a list of scores by hole for the backnine holes; (l) score in 942—corresponding to stroke total for thescores entered on the back nine; (m) stroke total 943—corresponding to astroke total for the round; or (n) combination thereof. In variousembodiments, the stroke total 943 will only be displayed when score out940 and score in 942 have data.

According to various embodiments, the round management system may beutilized to manage rounds and groupings for players competing in a golftournament. For example, the groupings engine may create playergroupings for the competing players. The round management system mayalso populate the ST application with the groupings from which scorersusing companion devices may identify groups and/or players for whichthey are assigned and will track scoring during the competition.

The grouped players may automatically populate a device assignmentelement of the device management system. Having the groups defined, thedevice management system may assign tracking modules from a device listto the various groups and players. In one example, companion devices orST application executed thereon are assigned or programmed to a specificgroup and the tracking modules assigned to the group may populate thecompanion device via the ST application for specific identification bythe scorer that links the scoring data to the tracking module. In onevariation, the scorer assigned to a group may enter their credentials orotherwise log onto the ST application whereby the group information ofthe group assigned to the scorer populates the ST application. Inanother configuration, entry of the player's name in the ST applicationidentifies the player for scoring data transmissions and one or more ofthe location system, data management system, or validation system isconfigured to access the tracking module assignments to pair the scoringdata with the tracking module data.

During the round, the scorer may collect scoring data by enteringvarious stroke events and other data into the companion device asdescribed herein. Stroke events may be associated with a time stamp. Thecompanion device may transmit the scoring data to the management system.The tracking module may automatically collect location data or locatingdata continuously, at defined intervals, or upon occurrence of definedevents. In one example, the tracking module is configured to obtain GPScoordinates corresponding to its location continuously, e.g., everysecond. The tracking module may automatically transmit the obtainedcoordinates to the management system continuously, at defined intervals,or upon occurrence of defined events. In one example, the trackingmodule transmits collected location data or locating data to themanagement system every five seconds. As noted above, other locationmethodologies may be used instead of, in addition to, or in combinationwith, e.g., a hybrid methodology, GPS. For instance, the STTM system mayinclude or incorporate a location network comprising an UWB locationnetwork. The location data or locating data may be transmitted to themanagement system directly or indirectly from the tracking module,location network, or other device.

The location system may access tracking module assignments and pair timestamps to locations of assigned tracking modules. The data managementsystem may access the scoring data where it may be reviewed and editedas necessary with the data management tool. The validation system maythen compare the score tracking system scores with scorecards of therespective players. For example, the validation system may apply blindvalidation. The validation system may then reconcile the score trackingsystem scores with the player scorecards. The validation system may thenmark the reconciled system obtained score as “official”. The “official”designation may then populate the data management tool interfaces toindicate that no additional scores or score modifications will beentered for the player. The official score and related data collected bythe companion device and tracking module during play may then be storedin a database and/or disseminated to data platforms for viewing,analysis, or the like.

In various embodiments, the score tracking system may utilize additionallocation tracking techniques. Such techniques may operate as a primary,secondary, backup, or replacement location determination methodologywith respect to utilization of the tracking module.

In one embodiment, the companion device or another electronic device isequipped with a laser rangefinder is operated by a scorer, e.g., humanor robot. The rangefinder is used to determine distance of objects, suchas players or balls, from the device. The device may also include adirection sensors, such as magnetic and/or gravitational field sensors,to combine distance and direction relative to a map of the course. Tofurther enhance location determination, the location of the device maybe known due to the device being located at a known location or thelocation of the device being determined by the device or another devicewhereby the location of the device, e.g., coordinates, are combined withthe angle and distance of the object from the device. For example, adevice in a mobile use case may obtain its GPS (or other globalconstellation coordinates), which may be augmented as described herein,e.g., with WAAS (Wide Area Augmentation System), Differential GPS(DGPS), e.g., Global Differential GPS (GDGPS), Continuously OperatingReference Stations (CORS), Signals of Opportunity (SOP)-based oraugmented navigation, UWB, LTE, cellular, radio, television, Wi-Fi,other satellite signals, or the like. Location of the device may also bedetermined using any location network technology, such as thosedescribed herein, e.g., utilizing UHF, NFC, Wi-Fi, Bluetooth Low-Energy,or UWB. Determining the coordinates of the object, the coordinates maybe overlaid or mapped to the golf course to determine the location ofthe object relative to the golf course. In one embodiment, the device isa real time kinematic (RTK) enabled device and utilizes RTK to determineits coordinates. For example, an RTK base station or network may beutilized to determine the location of the device for combining withdirection and distance of an object targeted with the laser rangefinderto determine object locations. Notably, as described elsewhere herein,the tracking module may similarly be an RTK enabled device and thelocation network may include an RTK base station or RTK network.

In one embodiment, a camera system is positioned around a golf course.One or more cameras may track movement and identify distance using anassociated laser or rangefinder or via optical calculations. Forexample, each camera may calculate the distance a ball or other objectof known size by comparing the optically captured size of the object tothat of the known size of the object. Further determination of the angleof the camera may be used to plot the location of the object at thedistance and angle from the camera relative to a map of the regionaround the camera. Location determination may be enhanced utilizingmultiple cameras, e.g., to triangulate or otherwise determine locationof a ball or other object. In one example, an optical map of a region ofthe course from a view of a fixed camera may be utilized by a camera todetermine location of objects relative to known locations within themapped region. For example, by comparing an image captured of an objectto surrounding features in the image of known location, the approximatelocation of the object may be determined. Optical calculations such asthose described above may be used to determine distance to enhance theaccuracy of the location determination. In an above or another example,radar may be implemented to track objects, which may include location,velocity, trajectory, acceleration, or other parameters. In an above oranother example, cameras may be configured for optical recognition. Forinstance, cameras may utilize facial recognition, body recognition, gaitrecognition, clothing recognition, ball/shape recognition, or the likethat is used to identify participants and/or balls to thereby pairlocation with player and/or player ball. In one embodiment, a playerscarry or wear an optical, electromagnetic, or reflective makeridentifiable by a camera or associated receiver that uniquely identifiesthe player. In one embodiment, cameras may utilize opticalrecognition/augmented reality (AR) to locate players and/or balls.Cameras may typically be located at known locations, but in someinstances one or more cameras may be utilized in a mobile environment,e.g., utilizing real time kinematic base stations or locationmethodologies with respect to the camera, such as those described hereinwith respect to location determination of the tracking module. In someembodiments, cameras may be used to identify motion and objects and alaser or rangefinder associated with a camera may target such objects todetermine distance of the object from the camera. Combining camera viewangle with distance, the location of the object may be determined. Insome embodiments, topology of the region may be mapped or determined andadded to the distance calculations. In some embodiments, such camerasystems are operated by a human, robot, or fully autonomous. Cameras mayoperate in the visual spectrum and/or optical spectrum to include one ormore of the visual spectrum, ultraviolet spectrum, or infrared spectrum.

The systems and methods disclosed herein may include still furtherfunctionalities and features. For example, the operative functions ofthe system and method may be configured to execute on a special-purposeprocessor specifically configured to carry out the operations providedby the system and method. Notably, the operative features andfunctionality provided by the system and method may increase theefficiency of computing devices that are being utilized to facilitatethe functionality provided by the system and the various methodsdisclosed herein. For example, by training the system over time based ondata and/or other information provided and/or generated in the system, areduced amount of computer operations may need to be performed by thedevices and elements in the system using the processors and memories ofthe system than compared to traditional methodologies. In such acontext, less processing power needs to be utilized because theprocessors and memories do not need to be dedicated for processing. As aresult, there are substantial savings in the usage of computer resourcesby utilizing the software, techniques, and algorithms provided in thepresent disclosure. In certain embodiments, various operativefunctionality of the system may be configured to execute on one or moregraphics processors and/or application specific integrated processors.In some embodiments, various functions and features of the system andmethods may operate without any human intervention and may be conductedentirely by computing devices. In certain embodiments, for example,numerous computing devices may interact with devices of the system toprovide the functionality supported by the system. Additionally, incertain embodiments, the computing devices of the system may operatecontinuously and without human intervention to reduce the possibility oferrors being introduced into the system.

At least a portion of the methodologies and techniques described withrespect to the exemplary embodiments may incorporate a machine, such as,but not limited to a computer system or other computing device withinwhich a set of instructions, when executed, may cause the machine toperform any one or more of the methodologies or functions discussedabove. The machine may be configured to facilitate various operationsconducted by the systems. For example, the machine may be configured to,but is not limited to, assist the systems by providing processing powerto assist with processing loads experienced in the systems, by providingstorage capacity for storing instructions or data traversing thesystems, or by assisting with any other operations conducted by orwithin the systems. As another example, the computer system may assistwith enhancing accuracy of collected scoring data collected in a reducedinfrastructure environment by incorporating rules such as error and/orwarning rules that automatically identify potential discrepancies. Asanother example, utilizing a tracking module that does not interferewith performance of a player or require player interaction to tracklocation provides accurate tracking that greatly reduces infrastructureand human intervention compared to current methodologies.

In some embodiments, the machine may operate as a standalone device. Insome embodiments, the machine may be connected (e.g., usingcommunications network, another network, or a combination thereof) toand assist with operations performed by other machines and systems, suchas, but not limited to, the tracking module, companion device,management device and associated system servers, database, any othersystem, program, and/or device, or any combination thereof. The machinemay be connected with any component in the systems. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in a server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment. Themachine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a laptop computer, a desktopcomputer, a control system, a network router, switch or bridge, or anymachine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while a single machine is illustrated, the term “machine” shall also betaken to include any collection of machines that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methodologies discussed herein.

The computer system may include a processor (e.g., a central processingunit (CPU), a graphics processing unit (GPU), or both), a main memoryand a static memory, which communicate with each other via a bus. Thecomputer system may further include a video display unit, which may be,but is not limited to, a liquid crystal display (LCD), a flat panel, asolid state display, or a cathode ray tube (CRT). The computer systemmay include an input device, such as, but not limited to, a keyboard, acursor control device, such as, but not limited to, a mouse, a diskdrive unit, a signal generation device, such as, but not limited to, aspeaker or remote control, and a network interface device. The diskdrive unit may include a machine-readable medium on which is stored oneor more sets of instructions, such as, but not limited to, softwareembodying any one or more of the methodologies or functions describedherein, including those methods illustrated above. The instructions mayalso reside, completely or at least partially, within the main memory,the static memory, or within the processor, or a combination thereof,during execution thereof by the computer system. The main memory and theprocessor also may constitute machine-readable media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Applications that may include the apparatusand systems of various embodiments broadly include a variety ofelectronic and computer systems. Some embodiments implement functions intwo or more specific interconnected hardware modules or devices withrelated control and data signals communicated between and through themodules, or as portions of an application-specific integrated circuit.Thus, the example system is applicable to software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein are intended for operation as software programsrunning on a computer processor. Furthermore, software implementationscan include, but not limited to, distributed processing orcomponent/object distributed processing, parallel processing, or virtualmachine processing can also be constructed to implement the methodsdescribed herein.

The present disclosure contemplates a machine-readable medium containinginstructions so that a device connected to the communications network,another network, or a combination thereof, can send or receive voice,video or data, and communicate over the communications network, anothernetwork, or a combination thereof, using the instructions. Theinstructions may further be transmitted or received over thecommunications network, another network, or a combination thereof, viathe network interface device. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” shall also be taken to include any medium thatis capable of storing, encoding or carrying a set of instructions forexecution by the machine and that causes the machine to perform any oneor more of the methodologies of the present disclosure. The terms“machine-readable medium,” “machine-readable device,” or“computer-readable device” shall accordingly be taken to include, butnot be limited to: memory devices, solid-state memories such as a memorycard or other package that houses one or more read-only (non-volatile)memories, random access memories, or other re-writable (volatile)memories; magneto-optical or optical medium such as a disk or tape; orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. The “machine-readable medium,” “machine-readable device,” or“computer-readable device” may be non-transitory, and, in certainembodiments, may not include a wave or signal per se. Accordingly, thedisclosure is considered to include any one or more of amachine-readable medium or a distribution medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

The illustrations of arrangements described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Other arrangements may be utilized andderived therefrom, such that structural and logical substitutions andchanges may be made without departing from the scope of this disclosure.Figures are also merely representational and may not be drawn to scale.Certain proportions thereof may be exaggerated, while others may beminimized. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

Thus, although specific arrangements have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific arrangementshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments and arrangements of the invention.Combinations of the above arrangements, and other arrangements notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description. Therefore, it is intended thatthe disclosure not be limited to the particular arrangement(s) disclosedas the best mode contemplated for carrying out this invention, but thatthe invention will include all embodiments and arrangements fallingwithin the scope of the appended claims.

The foregoing is provided for purposes of illustrating, explaining, anddescribing embodiments of this invention. Modifications and adaptationsto these embodiments will be apparent to those skilled in the art andmay be made without departing from the scope or spirit of thisinvention. Upon reviewing the aforementioned embodiments, it would beevident to an artisan with ordinary skill in the art that saidembodiments can be modified, reduced, or enhanced without departing fromthe scope and spirit of the claims described below.

1-28. (canceled)
 29. A golf tournament tracking system to track movementand location of players, balls, or both during play of a golftournament, the system comprising: a plurality of cameras positionedaround a golf course; a processor; and a memory storing instructionsthat when executed by the processor perform operations of the system,the operations comprising: capturing optical images with the pluralityof cameras during play of a golf tournament to track movement of aplayer, ball, or both by tracking its location on the golf course duringplay, determining location of a player, ball, or both captured in anoptical image by a first camera using an optical map of a region of thegolf course around the first camera, the location estimated relative toknown locations in the mapped region by comparing the image of theplayer, ball, or both to surrounding features of known location in theoptical image, and repeating the determination of location of theplayer, ball, or both in subsequent optical images to track movement ofthe player, ball, or both on the golf course during play of the golftournament.
 30. The system of claim 29, wherein the operations furthercomprise determining distance of the player, ball, or both from thefirst camera using optical calculations comprising comparing opticallycaptured size of the player or ball in the optical image to a known sizeof the player or ball.
 31. The system of claim 29, wherein theoperations further include determining distance of the player, ball, orboth from the first camera using a laser associated with the firstcamera and enhancing the location determination by using a view angle ofthe first camera and the determined distance to identify the location ofthe player, ball, or both relative to a map of the region.
 32. Thesystem of claim 29, wherein the system utilizes object recognition toidentify players, balls, or both in the optical images, wherein theobject recognition comprises facial recognition, body recognition, gaitrecognition, or clothing recognition to identify the player in theoptical images and shape recognition to identify balls in the opticalimages.
 33. The system of claim 29, wherein the system utilizes facialrecognition, body recognition, gait recognition, or clothing recognitionto identify the player in the optical images and shape recognition toidentify balls in the optical images to pair the determined locationswith the corresponding player, ball, or player and player's ball. 34.The system of claim 29, wherein the operations further compriseidentification of the player via optical, electromagnetic, or reflectivemarkers worn or carried by the player that uniquely identifies theplayer using the camera or an associated receiver.
 35. The system ofclaim 29, wherein the operations further include tracking one or moreball flight parameters selected from location, velocity, trajectory, oracceleration using radar.
 36. A method of tracking movement and locationof players, balls, or both during play of a golf tournament, the methodcomprising: capturing, with a plurality of cameras positioned around agolf course, optical images of players, balls, or both during play of agolf tournament, tracking movement of the players, balls, or both in thecaptured images by tracking their location on the golf course duringplay, determining location of a player, ball, or both captured in anoptical image by a first camera using an optical map of a region of thegolf course around the first camera, the location estimated relative toknown locations in the mapped region by comparing the image of theplayer, ball, or both to surrounding features of known location in theoptical image, and repeating the determination of location of theplayer, ball, or both in subsequent optical images to track movement ofthe player, ball, or both on the golf course during play of the golftournament.
 37. The method of claim 36, further comprising determiningdistance of the player, ball, or both from the first camera usingoptical calculations comprising comparing optically captured size of theplayer or ball in the optical image to a known size of the player orball.
 38. The method of claim 36, determining distance of the player,ball, or both from the first camera using a laser associated with thefirst camera and enhancing the location determination by using a viewangle of the first camera and the determined distance to identify thelocation of the player, ball, or both relative to a map of the region.39. The method of claim 36, further comprising utilizing objectrecognition to identify players, balls, or both in the optical images,wherein the object recognition comprises facial recognition, bodyrecognition, gait recognition, or clothing recognition to identify theplayer in the optical images and shape recognition to identify balls inthe optical images.
 40. The method of claim 39, further comprisingpairing the determined locations with the corresponding identifiedplayer, ball, or player and player's ball.
 41. The method of claim 36,further comprising identifying the player via optical, electromagnetic,or reflective markers worn or carried by the player that uniquelyidentifies the players using the camera or an associated receiver. 42.The method of claim 36, further comprising tracking one or more ballflight parameters selected from location, velocity, trajectory, oracceleration using radar.
 43. A golf tournament tracking system to trackmovement and location of players, balls, or both during play of a golftournament, the system comprising: a plurality of cameras positionedaround a golf course; a processor; and a memory storing instructionsthat when executed by the processor perform operations of the system,the operations comprising: capturing optical images with the pluralityof cameras during play of a golf tournament to track movement ofplayers, balls, or both by tracking their location on the golf courseduring play, determining, using optical calculations applied to anoptical image captured by a first camera, distance of a player, ball, orboth from the first camera captured the optical image comprisingcomparing an optically captured size of the player or ball in theoptical image to a known size of the respective player or ball, plottingthe location of the player, ball, or both relative to a map of a regionof the golf course around the first camera using a view angle of thefirst camera and the determined distance, and repeating thedetermination of location of the player, ball, or both in subsequentoptical images to track movement of the player, ball, or both.
 44. Thesystem of claim 43, wherein the system is configured to enhance thedistance determination using a laser associated with the first camera.45. The system of claim 43, wherein the operations further comprisecapturing optical images of the players, balls, or both at the same timefrom different cameras and determining distance of the players, balls,or both from the cameras capturing the respective images to enhance alocation determination.
 46. The system of claim 43, wherein the systemutilizes object recognition to identify players, balls, or both in theoptical images, wherein the object recognition comprises facialrecognition, body recognition, gait recognition, or clothing recognitionto identify the player in the optical images and shape recognition toidentify balls in the optical images.
 47. The system of claim 43,wherein the system utilizes facial recognition, body recognition, gaitrecognition, or clothing recognition to identify the players in theoptical images and shape recognition to identify balls in the opticalimages to pair the locations with the corresponding identified player,ball, or player and player's ball.
 48. The system of claim 43, whereinthe operations further comprise identification of players via optical,electromagnetic, or reflective markers worn or carried by the playersthat uniquely identify the players using the camera or an associatedreceiver.
 49. The system of claim 43, wherein topology of the region ismapped or determined and utilizes in the distance determinations. 50.The system of claim 43, wherein the first camera includes a directionsensor comprising a magnetic field sensor, gravitational field sensor,or both.
 51. A method of tracking movement and location of players,balls, or both during play of a golf tournament, the method comprising:capturing, with a plurality of cameras positioned around a golf course,optical images of players, balls, or both during play of a golftournament, tracking movement of players, balls, or both in the capturedimages by tracking their location on the golf course during play,determining, using optical calculations applied to an optical imagecaptured by a first camera, distance of a player, ball, or both from thefirst camera captured the optical image comprising comparing anoptically captured size of the player or ball in the optical image to aknown size of the respective player or ball, plotting the location ofthe player, ball, or both relative to a map of a region of the golfcourse around the first camera using a view angle of the first cameraand the determined distance, and repeating the determination of locationof the player, ball, or both in subsequent optical images to trackmovement of the player, ball, or both.
 52. The method of claim 51,further comprising enhancing the distance determination using a laserassociated with the first camera.
 53. The method of claim 51, furthercomprising utilizing object recognition to identify players, balls, orboth in the optical images, wherein the object recognition comprisesfacial recognition, body recognition, gait recognition, or clothingrecognition to identify the player in the optical images and shaperecognition to identify balls in the optical images.
 54. The method ofclaim 53, further comprising pairing the locations with thecorresponding identified player, ball, or player and player's ball. 55.The method of claim 51, further comprising identifying players viaoptical, electromagnetic, or reflective markers worn or carried by theplayers that uniquely identify the players using the camera or anassociated receiver.
 56. The method of claim 51, further comprisingtracking one or more ball flight parameters selected from location,velocity, trajectory, or acceleration using radar.
 57. The method ofclaim 51, wherein the first camera includes a direction sensorcomprising a magnetic field sensor, gravitational field sensor, or both.